Connect ChatGPT or an OAuth MCP Client to Thegram Cloud

@gram 2
doc d_20b2aa2bd782451d88e528a4d5ca468d
t Connect ChatGPT or an OAuth MCP Client to Thegram Cloud
::rich
# Connect to Thegram Cloud

Thegram Cloud is the hosted Streamable HTTP MCP route at https://vault.thegram.one/mcp. It uses OAuth. It works while the Mac is off. Local Mac-only folders are not exposed by this service. The Cloud vault is available to the current signed-in identity; Google Drive is a separate storage connection and is not enabled just by signing in.

## Prerequisites

- A Thegram account. The hosted guide says account creation completes when a person signs in; follow its sign-up and age/terms prompts directly.
- ChatGPT for the ChatGPT-specific flow, or an MCP client that supports Streamable HTTP and OAuth for a generic connection.
- A person must review and authorize the named account in the provider UI. Do not authorize or change account/connection state on the person's behalf.

## ChatGPT chats and dots

Follow [the canonical ChatGPT install guide](https://thegram.one/install/chatgpt.md): open chatgpt.com/plugins (or ChatGPT Mac Settings → Plugins → Browse directory), choose Add → Create custom MCP server, set name gram, URL https://vault.thegram.one/mcp, Authentication OAuth, then Create as plugin. Continue to gram, check the account name on the Thegram page, and let the person choose Authorize. In a chat or dot, select + → gram under Plugins to make @gram available.

The source guide reports that its ChatGPT Mac app install sequence was verified. It mentions dots as a usage surface, but this evidence does not claim an independently tested dot installation. The optional private-plugin ZIP update adds a skill; it is not required to connect the server tools and is outside this read-only first check.

## Generic OAuth MCP clients

Configure the client with endpoint https://vault.thegram.one/mcp, Streamable HTTP and OAuth, then follow that client's own sign-in UI. The source-backed capability is the published endpoint/transport/authentication information. Do not copy ChatGPT-specific buttons or claim an unobserved generic provider's exact UI, token flow or setup command.

## Verify read-only

1. Call gram_capabilities and gram_projects. Expect the tools available to this session and the current identity's authorized vault/mounts.
2. Use an exact path or mount key returned by gram_projects. Call gram_brief for that path, then gram_read with outline=true; read a section only by a heading returned in that outline.
3. Expected result: the correct authorized vault/document is visible and current content is returned with revision/hash context. This does not authorize writing or make connected apps' content eligible to save.
4. Keep this first check read-only. Reading, searching, analysis and drafts remain read-only; writing requires a separate explicit request and appropriate access.

## Troubleshooting

- ChatGPT returns 401 or loops at sign-in: remove the gram plugin in ChatGPT and repeat its canonical Part 2 with the intended account.
- CONSENT_REQUIRED: the person finishes sign-up at https://vault.thegram.one before any retry.
- gram_projects shows no vault: the guide says the first connection creates the Thegram vault; if it remains missing after a second read-only check, contact support@thegram.one. Do not create a vault yourself.
- PROVIDER_AUTH_REQUIRED: the person reconnects that Google Drive under vault.thegram.one → Settings → Connections. Do not write elsewhere as a fallback.
- E_FORBIDDEN: the identity has viewer access; ask the vault owner for editor access or inspect another already-authorized mount.

Sources: https://thegram.one/install/chatgpt.md · https://thegram.one/agent-memory/#cloud · https://github.com/clab-one/thegram-plugin/blob/master/skills/thegram-cloud/SKILL.md
::end