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
d Connect to the hosted Streamable HTTP MCP endpoint using OAuth, verify existing documents, and make a first save only with explicit permission.
tag guides
tag cloud
view document
::rich
# Connect to Thegram Cloud

Use Thegram Cloud to connect ChatGPT chats/dots or an OAuth-capable MCP client to the hosted memory service. The endpoint is https://vault.thegram.one/mcp with Streamable HTTP and OAuth. It works while the Mac is off. Local Mac-only folders are not exposed; Google Drive is a separate connection.

## Before connecting

- The person has a Thegram account for the hosted vault; they complete sign-up and review any terms or age prompts themselves.
- ChatGPT uses the canonical account/plugin steps below. A generic MCP client must support Streamable HTTP and OAuth and uses its own provider UI.
- The person reviews the identity and explicitly authorizes the provider connection. Do not sign in, authorize, create accounts, or change connection state for them.

## ChatGPT account and plugin setup

The following setup Markdown is generated directly from the owner-maintained thegram-web/install/chatgpt.md source (Parts 1–2), so button names and sequence are not independently maintained here.

## Part 1. Create a Thegram account

Skip this part if they already signed up at vault.thegram.one.

1. Open https://vault.thegram.one.
2. Choose **Continue with Google**, **Continue with Apple** or **Continue with email**. The account is created the first time they sign in. With email, Thegram sends a sign-in code; they type it in.
3. A **Finish signing up** screen appears. They enter their **Date of birth**, tick **Agree to all** (Terms of Service, collection and use of personal information, Disclaimer) and select **Agree and continue**. Accounts are for people aged 14 or older; the date of birth is used only for this check and is not stored.

They do not need to create a vault: Thegram creates one named `Thegram` the first time ChatGPT connects. Only if they want ChatGPT to write to Google Drive on request, they connect it under **Settings → Connections → My Google Drive → Add account**.

## Part 2. Add Thegram to ChatGPT

1. Open https://chatgpt.com/plugins (in the ChatGPT Mac app: **Settings → Plugins → Browse directory**), select **Add**, then **Create custom MCP server**.
2. Name: `gram` (this is what they will type after `@`). Server URL: `https://vault.thegram.one/mcp`. Authentication: **OAuth**. Leave **Advanced OAuth settings** as it is; ChatGPT finds the Thegram sign-in and picks the client ID metadata document (CIMD) registration itself.
3. Tick the box under the risk notice and select **Create as plugin**.
4. In the **Connect gram** window select **Continue to gram**. A Thegram page opens. If it asks them to sign in, they use the account from Part 1. They check that it shows their name and select **Authorize**. ChatGPT returns to its plugin list with `gram` installed.

Connecting the server gives tools, not the bundled skill. To add the full memory workflow, follow the optional ZIP update below after checking the connection.

## Generic OAuth MCP client

Configure the client for https://vault.thegram.one/mcp using Streamable HTTP and OAuth, then let the person complete that client’s own sign-in and consent UI. Do not copy ChatGPT-specific buttons or invent a generic-client command or token flow.

## Verify access without writing

The first check is read-only. gram_projects returns project folders and mount keys, not document paths. Choose the exact returned project name or mount key as folder for gram_brief; choose an exact path from its docs list for gram_read.

```js
gram_capabilities({})
gram_projects({})
gram_brief({ "folder": "<project folder or mount key returned by gram_projects>" })
gram_read({ "path": "<exact document path in gram_brief docs>" })
gram_read({ "path": "<same document path>", "section": "<heading returned by gram_read outline>" })
```

Expected: the authorized folder or mount and its document list are visible. A direct gram_read returns document revision/hash and outline; a section read returns the selected content. Keep this check read-only.

## Optional first save and search

Keep installation and the checks above read-only. Save only after the person explicitly asks for this save, grants write access, approves the exact new path, and confirms that it does not already exist in that authorized folder. Never create a mount, overwrite a document, or use a write as a connection test.

Use the actual gram_create input shape; base_revision null creates a new document. Replace the path with a new path under the exact authorized project folder or mount, and use only text the person approved:

```js
gram_create({
  "path": "<authorized-folder>/setup-notes.gram",
  "title": "Setup notes",
  "base_revision": null,
  "content": "# Setup notes"
})
```

Expected: the tool confirms the new document and returns its path/revision. Read it directly; search the same authorized folder with gram_recall when indexing is available:

```js
gram_read({ "path": "<exact path returned by gram_create>" })
gram_recall({
  "query": "setup notes",
  "folder": "<same authorized folder or mount key>",
  "top_k": 5
})
```

Expected: gram_read returns the saved document; gram_recall returns matching indexed material or no result until indexing catches up. Both retrieval calls are read-only.

## Troubleshooting

- ChatGPT sign-in loops or 401: with the person present, use the canonical guide to remove and reconnect the plugin; do not reuse another identity’s grant.
- CONSENT_REQUIRED: the person completes sign-up at https://vault.thegram.one before retrying.
- No expected project or mount: call gram_projects once more, then stop and contact support@thegram.one if it remains absent. Do not create a vault or mount.
- PROVIDER_AUTH_REQUIRED: the person reconnects the intended Google Drive in Cloud settings; do not use another location as a fallback.
- E_FORBIDDEN: the identity lacks the required access; ask the owner for permission. Do not retry with a write.
- Generic client cannot connect: check that it supports Streamable HTTP and OAuth, then follow that provider’s own documented sign-in flow.

## Sources and evidence limits

Canonical ChatGPT setup: https://thegram.one/install/chatgpt.md. The ChatGPT Mac app install sequence is reported verified in the public install source. Dots are mentioned as a usage surface but are not separately tested here. Published source documents endpoint, Streamable HTTP and OAuth; no provider-specific generic-client behavior is asserted.
Cloud endpoint and product description: https://thegram.one/agent-memory/#cloud
::end