@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

@gram-history 6
@rev 0 2026-10-12T13:01:57.755Z agent agent=omp-coding-agent df095fd61f2f1d5e9dfd3cfa9af79eed195b307369839d4446a85425ed69168e
@rev 1 2026-10-12T13:06:47.782Z agent agent=omp-coding-agent req=product-cloud-setup-canonical-handoff-20261012 dig=93e1c7ba1f1beabe 4d2194d261b779b3617c36abdca3e4f1b690668ec1db0162f43f415f56d92f9b
@@ 16 1 3
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.
@rev 2 2026-10-12T13:38:02.528Z portal-product-quickstarts agent=developer-doc-generator req=portal-product-cloud-setup-670f24b5552a6429f2c8985d dig=d0041347ff20390e kind=SourceImported 9e1bc10a552f3d70db05a26035bbc8a5db3251c5939f7a80d5704f29aa009bfc
@@ 3 5 1
::rich
@@ 10 1 1
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.
@@ 12 1 1
## Prerequisites
@@ 14 3 3
- 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.
@@ 18 1 1
## ChatGPT chats and dots
@@ 20 1 1
For exact account, plugin, OAuth consent and in-chat steps, follow Part 1–3 of the [canonical ChatGPT install guide](https://thegram.one/install/chatgpt.md). This Docs page deliberately does not maintain a second click-by-click flow. The guide reports that its ChatGPT Mac app install sequence was verified. It mentions dots as a usage surface, but no separate dot installation test is claimed here. The optional private-plugin ZIP update adds a skill and is distinct from connecting server tools; it is not required for this read-only first check.
@@ 22 0 4
## 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.

@@ 24 3 4
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.
@@ 30 5 5
- 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.
@@ 36 1 1
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
@rev 3 2026-10-12T13:47:34.205Z portal-product-quickstarts agent=developer-doc-generator req=portal-product-cloud-setup-e966effbcc78dbedab558190 dig=65eacac100e67eb9 kind=SourceImported bb37f5d613861d1cf44b12a6d9e0a270f528bd6cd2a43e2db4988818d3ef8e70
@@ 7 1 1
::body
@rev 4 2026-10-12T14:10:29.199Z portal-product-quickstarts agent=developer-doc-generator req=portal-product-cloud-setup-fc3314b7928e2963e0107223 dig=28f372abfadcb283 kind=SourceImported 3e317778ebf9fa3cc7e92059925c1bc53be99253cc50606bea4c9d823fd0c6b4
@@ 3 1 1
d Connect to the hosted Streamable HTTP MCP endpoint using OAuth, distinguish provider evidence, and verify read-only access.
@@ 10 1 1
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.
@@ 12 1 1
## Prerequisites and consent
@@ 14 3 3
- 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.
@@ 18 1 1
## ChatGPT, dots, and generic clients
@@ 20 1 1
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.
@@ 22 1 1
## Verify read-only
@@ 24 1 3
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.
@@ 26 61 0
@@ 89 1 1
- ChatGPT sign-in loops: follow the canonical guide’s account and plugin reconnect steps with the person present.
@@ 91 4 3
- 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.
@@ 96 4 1
Sources: https://thegram.one/install/chatgpt.md · https://thegram.one/agent-memory/#cloud