Getting Started
Connect ChatGPT or an OAuth MCP Client to Thegram Cloud
Connect to the hosted Streamable HTTP MCP endpoint using OAuth, distinguish provider evidence, and verify read-only access.
Explore as .gram
Document
Text
# Connect to Thegram Cloud
The hosted endpoint is https://vault.thegram.one/mcp, using Streamable HTTP and OAuth. It works while the Mac is off. Local Mac-only folders are not exposed. Google Drive is separate and is not enabled by signing in.
## Prerequisites and consent
- A Thegram account for the hosted vault.
- ChatGPT for its documented UI flow, or an MCP client supporting Streamable HTTP and OAuth.
- The person reviews and authorizes the intended identity in the provider UI. Do not create accounts or change account/connection state on their behalf.
## ChatGPT, dots, and generic clients
For exact account, plugin, OAuth consent and in-chat steps, use the [canonical ChatGPT install guide](https://thegram.one/install/chatgpt.md); this page does not duplicate those steps. The ChatGPT Mac app install sequence is reported verified in the public install source. Dots are mentioned as a usage surface; no separate dot-install test is claimed. Published source documents endpoint, Streamable HTTP and OAuth; no provider-specific generic-client behavior is asserted.
## Verify read-only
1. Call gram_capabilities and gram_projects; use the exact mount key/path returned.
2. Call gram_brief for that path, then gram_read without section to obtain the outline and gram_read with a returned heading as section.
3. Expected: the intended authorized vault/document appears with current revision and content. Keep this first check read-only; do not create a vault or use writes as fallback.
## Troubleshooting
- ChatGPT sign-in loops: follow the canonical guide’s account and plugin reconnect steps with the person present.
- CONSENT_REQUIRED: the person completes sign-up at https://vault.thegram.one before retrying.
- No vault appears: follow the canonical guide; if still absent, contact support@thegram.one. Do not create a vault yourself.
- PROVIDER_AUTH_REQUIRED: the person reconnects the intended Google Drive in Cloud settings.
- E_FORBIDDEN: ask the vault owner about access; do not write elsewhere as fallback.
Sources: https://thegram.one/install/chatgpt.md · https://thegram.one/agent-memory/#cloud
r2 · · Portal-product-quickstarts
Connect to the hosted Streamable HTTP MCP endpoint using OAuth, distinguish provider evidence, and verify read-only access.
0Needs attention
Nothing to show in this revision
r2 source2406 bytes ·
sha256:670f24b5552a6429f2c8985d2286c902b67a8ebbfe2f660ed264929e0180acf9@gram 2
doc d_20b2aa2bd782451d88e528a4d5ca468d
t Connect ChatGPT or an OAuth MCP Client to Thegram Cloud
d Connect to the hosted Streamable HTTP MCP endpoint using OAuth, distinguish provider evidence, and verify read-only access.
tag guides
tag cloud
view document
::body
# Connect to Thegram Cloud
The hosted endpoint is https://vault.thegram.one/mcp, using Streamable HTTP and OAuth. It works while the Mac is off. Local Mac-only folders are not exposed. Google Drive is separate and is not enabled by signing in.
## Prerequisites and consent
- A Thegram account for the hosted vault.
- ChatGPT for its documented UI flow, or an MCP client supporting Streamable HTTP and OAuth.
- The person reviews and authorizes the intended identity in the provider UI. Do not create accounts or change account/connection state on their behalf.
## ChatGPT, dots, and generic clients
For exact account, plugin, OAuth consent and in-chat steps, use the [canonical ChatGPT install guide](https://thegram.one/install/chatgpt.md); this page does not duplicate those steps. The ChatGPT Mac app install sequence is reported verified in the public install source. Dots are mentioned as a usage surface; no separate dot-install test is claimed. Published source documents endpoint, Streamable HTTP and OAuth; no provider-specific generic-client behavior is asserted.
## Verify read-only
1. Call gram_capabilities and gram_projects; use the exact mount key/path returned.
2. Call gram_brief for that path, then gram_read without section to obtain the outline and gram_read with a returned heading as section.
3. Expected: the intended authorized vault/document appears with current revision and content. Keep this first check read-only; do not create a vault or use writes as fallback.
## Troubleshooting
- ChatGPT sign-in loops: follow the canonical guide’s account and plugin reconnect steps with the person present.
- CONSENT_REQUIRED: the person completes sign-up at https://vault.thegram.one before retrying.
- No vault appears: follow the canonical guide; if still absent, contact support@thegram.one. Do not create a vault yourself.
- PROVIDER_AUTH_REQUIRED: the person reconnects the intended Google Drive in Cloud settings.
- E_FORBIDDEN: ask the vault owner about access; do not write elsewhere as fallback.
Sources: https://thegram.one/install/chatgpt.md · https://thegram.one/agent-memory/#cloud
::end