Getting Started
Thegram Quickstart: Choose Local or Cloud, Then Read Safely
Choose local Mac or Cloud, meet current source prerequisites, then verify read-only access.
Explore as .gram
Document
Text
# Thegram quickstart
Choose one connection: the local Mac MCP server for coding agents on the same Mac, or Thegram Cloud for ChatGPT/dots and OAuth-capable MCP clients. Local-only folders are not exposed to Cloud.
## Choose the connection
| Route | Prerequisites | First setup |
|---|---|---|
| Local coding agent | Apple silicon (arm64); macOS 26 or later; Node.js 22+; app open | The person enables Agent Access. Follow the [canonical local install guide](https://thegram.one/install/agents.md). |
| Thegram Cloud | Thegram account; ChatGPT or OAuth-capable MCP client | Use https://vault.thegram.one/mcp with Streamable HTTP and OAuth. ChatGPT follows its [canonical guide](https://thegram.one/install/chatgpt.md). |
## First check: read-only
Do not call gram_create or gram_patch during setup or this first check.
1. Call gram_capabilities. Expect available tools and server capacity; this does not prove a particular document is accessible.
2. Call gram_projects. Use only a returned project path or mount key; local Mac-only folders are not visible from Cloud.
3. Call gram_brief for an exact existing path returned by gram_projects. Expect title, current revision/hash, counts and recent changes.
4. Call gram_read for that path without section to receive its outline, then call gram_read again with a heading from that outline as section.
Sequence: gram_capabilities → gram_projects → gram_brief(path=<returned path>) → gram_read(path=<same path>) → gram_read(path=<same path>, section=<returned heading>). These calls are read-only.
## Expected result
The selected identity can see an authorized project or vault and an existing document with revision context; the focused read returns the requested section. Installation alone does not prove app availability, OAuth authorization or document scope. Stop on errors; do not change mounts or try writes as a connectivity check.
## Client distinctions
- Claude Code, Codex, OpenCode and OMP use the local Mac server; their commands and host prompts live only in the [canonical local install guide](https://thegram.one/install/agents.md).
- ChatGPT chats and dots use the Cloud endpoint and ChatGPT plugin/custom MCP UI. The ChatGPT Mac app install sequence is reported verified in the public install source.
- A generic MCP client must support Streamable HTTP and OAuth. Published source documents endpoint, Streamable HTTP and OAuth; no provider-specific generic-client behavior is asserted.
Sources: https://thegram.one/install/agents.md · https://thegram.one/install/chatgpt.md · https://thegram.one/agent-memory/
r1 source2851 bytes ·
sha256:8cbfe8bfee27b1474d3966f552150361ea2d640e1eaff4ebac78740fed8d75cd@gram 2
doc d_5778a001327643799617b998ea2e6e00
t Thegram Quickstart: Choose Local or Cloud, Then Read Safely
d Choose local Mac or Cloud, meet current source prerequisites, then verify read-only access.
tag guides
tag quickstart
view document
::body
# Thegram quickstart
Choose one connection: the local Mac MCP server for coding agents on the same Mac, or Thegram Cloud for ChatGPT/dots and OAuth-capable MCP clients. Local-only folders are not exposed to Cloud.
## Choose the connection
| Route | Prerequisites | First setup |
|---|---|---|
| Local coding agent | Apple silicon (arm64); macOS 26 or later; Node.js 22+; app open | The person enables Agent Access. Follow the [canonical local install guide](https://thegram.one/install/agents.md). |
| Thegram Cloud | Thegram account; ChatGPT or OAuth-capable MCP client | Use https://vault.thegram.one/mcp with Streamable HTTP and OAuth. ChatGPT follows its [canonical guide](https://thegram.one/install/chatgpt.md). |
## First check: read-only
Do not call gram_create or gram_patch during setup or this first check.
1. Call gram_capabilities. Expect available tools and server capacity; this does not prove a particular document is accessible.
2. Call gram_projects. Use only a returned project path or mount key; local Mac-only folders are not visible from Cloud.
3. Call gram_brief for an exact existing path returned by gram_projects. Expect title, current revision/hash, counts and recent changes.
4. Call gram_read for that path without section to receive its outline, then call gram_read again with a heading from that outline as section.
Sequence: gram_capabilities → gram_projects → gram_brief(path=<returned path>) → gram_read(path=<same path>) → gram_read(path=<same path>, section=<returned heading>). These calls are read-only.
## Expected result
The selected identity can see an authorized project or vault and an existing document with revision context; the focused read returns the requested section. Installation alone does not prove app availability, OAuth authorization or document scope. Stop on errors; do not change mounts or try writes as a connectivity check.
## Client distinctions
- Claude Code, Codex, OpenCode and OMP use the local Mac server; their commands and host prompts live only in the [canonical local install guide](https://thegram.one/install/agents.md).
- ChatGPT chats and dots use the Cloud endpoint and ChatGPT plugin/custom MCP UI. The ChatGPT Mac app install sequence is reported verified in the public install source.
- A generic MCP client must support Streamable HTTP and OAuth. Published source documents endpoint, Streamable HTTP and OAuth; no provider-specific generic-client behavior is asserted.
Sources: https://thegram.one/install/agents.md · https://thegram.one/install/chatgpt.md · https://thegram.one/agent-memory/
::end