connect an AI

innernet speaks MCP (Model Context Protocol). Anything MCP-aware can read and write your projects with one config line.

Claude Code#

One command:

claude mcp add --transport http innernet https://innernet.live/api/mcp

The browser sign-in runs on first tool call. From then on, every claude session can load and save your context maps.

Claude Desktop#

Open your dashboard's connections panel, press connect on Claude Desktop, sign in, approve. Manual install: add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "innernet": {
      "url": "https://innernet.live/api/mcp",
      "transport": "http"
    }
  }
}

Cursor#

Settings → MCP → Add Server. Paste the URL, let the OAuth sign-in run. Same flow for Cline, Continue, Zed, and any custom MCP client — URL-only config, no key.

ChatGPT (Deep Research connector)#

ChatGPT requires a confidential OAuth client. The connections flow generates one automatically — you'll see client_id and client_secret exactly once; paste both into ChatGPT's connector setup. ChatGPT drives innernet through its search and fetch tools, which run real full-text search over your maps.

protocol notes#

• Transport: streamable HTTP (single POST endpoint). Protocol revisions 2025-06-18, 2025-03-26, and 2024-11-05 are all accepted and negotiated on initialize.
• Resources: every project map is exposed as innernet://project/{slug}/map (JSON), and dimensions as innernet://project/{slug}/dimension/{name} (markdown).
• JSON-RPC batches are accepted.
• Rate limit: 240 calls/min per account — far above any real session.

API keys — CLI & scripts only#

For non-interactive access (the innernet CLI, cron, CI) mint a key at /developers and send it as Authorization: Bearer innernet_.... If an AI ever asks you to paste a key into chat to "connect innernet", that's wrong — give it the URL and let OAuth run.

trouble?#

curl https://innernet.live/api/mcp

You should get JSON with the tool list. HTML back means the URL is wrong; a 401 means the token is missing or expired (re-run the sign-in). Still stuck? The status endpoint and error shapes apply to MCP too.