Connect ChatGPT or an OAuth MCP Client to Thegram Cloud · r10

Archived revision r10, recorded 2026-10-14T04:39:45.729Z by portal-product-quickstarts. Current page: Connect ChatGPT or Claude to Thegram with OAuth.

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 install 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.

Local and Cloud: features, permissions and storage

Route	Features	Connection / permission	Storage
Local Mac (owner-source supported)	MCP; Document, Dashboard, Graph UI; gram_recall modes: exact, keyword, semantic, hybrid, auto; embeddinggemma-2 semantic retrieval is conditional on model/index readiness. Dynamic; check gram_capabilities semantic status and index counts before semantic retrieval.	Thegram for Mac running; Agent Access (read or write) granted by the person	Local Mac folders plus connected Google Drive and Thegram Cloud vault mounts listed by gram_projects; each mount reports its read/write access.
Cloud (user-reported 2026-10-13)	MCP (15 tools); Document, Dashboard; search: exact, keyword; semantic search: unavailable	Thegram account; OAuth sign-in; running Mac required: no	Thegram Cloud vaults or Google Drive separately connected at vault.thegram.one

Thegram for Mac 0.9.8 (build 33) was reported in use on 2026-10-13; this dated app observation is distinct from the current Mac release, which is sourced from thegram-desktop-release/evidence/release-200/verification.json. Cloud runtime facts are dated user-reported observations, not an independently captured runtime test. Provenance: User review supplied 2026-10-13; reported runtime observations, not an independently captured test.

ChatGPT install

The following three-step setup is generated directly from the owner-maintained thegram-web/install/chatgpt.md source, so its official link, button label and sequence are not independently maintained here.

Connect Thegram to ChatGPT

1. Open the official Thegram plugin page: https://chatgpt.com/plugins/plugin_asdk_app_6acc810ccabc8191acd3f457dc498d43
2. Select Install plugin and follow the installation and account-connection prompts shown in ChatGPT.
3. In a chat or dot, select Thegram from the available tools or apps.

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.

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:

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:

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 Cloud plugin source package version 1.5.4 is derived from owner package manifests. The public GitHub Release version 1.5.0 is separately user-reported as of 2026-10-13, not a value from those source manifests; these identifiers describe different artifacts. Provenance: User review supplied 2026-10-13; reported runtime observations, not an independently captured test.

Source and renderer evidence

Canonical source SHA-256

2b81848fae488b837fd67778b4f2495e811f987a640171b20cc232242627fa34

Selected revision

r10 · sha256:db2f817f6f65cc83b05175066970bd81b527beb2016554c030b49b5b69243a5c

Local renderer

configured local Thegram renderer · API thegram-web-render/1

Core source

git+https://github.com/clab-one/thegram-format.git?rev=b16489e1d0d77d38f82d2f61776524737aa31557#b16489e1d0d77d38f82d2f61776524737aa31557

Canonical source: 10.gram