Connect Claude Code, Codex & other AI tools (MCP)

Studiograph exposes an MCP (Model Context Protocol) server at your workspace’s /mcp endpoint. Any MCP-compatible tool — Claude Code, Codex, Claude Desktop, claude.ai, Cursor — can search, read, and edit your workspace through it, with the same folder access you have in the app. There are two ways to authenticate, and which one you want depends on whether a browser is available:

Method	Best for	How it works
Sign in through the browser (OAuth)	Interactive tools: Claude Desktop, claude.ai, Claude Code on your machine	Paste the endpoint URL; the tool opens a browser page where you approve access. No token to manage.
Personal access token	Headless sessions: CI, scripts, autonomous agents, Codex, servers without a browser	Mint an `sg_` token once and pass it as a Bearer header or environment variable.

Either way, the connection acts as you — the connected tool sees exactly the folders you can see, nothing more.

Find your endpoint URL

In the web app, open Settings → Agents. The MCP Access section shows your workspace’s endpoint URL (it ends in /mcp) with a copy button. This page is available to everyone, not just owners.

Mint a token (for headless clients)

Open Settings → Agents → Advanced

The Advanced disclosure below MCP Access holds your personal access tokens.

Create a token

Click New token, give it a name (for example “claude-code”), and create it. The token starts with sg_ and is shown once, together with a ready-to-paste client config — copy both now.

Claude Code

For an interactive session, add the server over HTTP and sign in through the browser:

claude mcp add --transport http studiograph https://<your-workspace>/mcp

Then run /mcp inside Claude Code and pick studiograph to complete the browser sign-in. For a headless session — CI, claude -p, or any machine where the browser flow isn’t an option — pass a personal access token instead:

claude mcp add --transport http studiograph https://<your-workspace>/mcp \
  --header "Authorization: Bearer sg_your_token_here"

To share the server with everyone working in a project, commit a .mcp.json at the project root (keep the token out of it — use an environment variable):

{
  "mcpServers": {
    "studiograph": {
      "type": "http",
      "url": "https://<your-workspace>/mcp",
      "headers": {
        "Authorization": "Bearer ${STUDIOGRAPH_MCP_TOKEN}"
      }
    }
  }
}

A one-off headless run can also load the config directly:

claude -p "Summarize this week's meeting notes from Studiograph" \
  --mcp-config .mcp.json

Codex

Add the server to ~/.codex/config.toml. Recent Codex versions connect to HTTP servers directly:

[mcp_servers.studiograph]
url = "https://<your-workspace>/mcp"
bearer_token_env_var = "STUDIOGRAPH_MCP_TOKEN"

Export STUDIOGRAPH_MCP_TOKEN=sg_your_token_here in the shell that launches Codex. If your Codex version doesn’t support URL-based servers, spawn the Studiograph CLI as a stdio server instead (requires the CLI and a local workspace — see Local workspace below):

[mcp_servers.studiograph]
command = "studiograph"
args = ["mcp", "/absolute/path/to/your/workspace"]
env = { "STUDIOGRAPH_MCP_TOKEN" = "sg_your_token_here" }

Claude Desktop and claude.ai

Both use the browser sign-in — no token needed:

Copy the endpoint URL from Settings → Agents → MCP Access.
In Claude, add a custom connector (or “MCP server”) and paste the URL.
Approve access in the browser window that opens.

Cursor and other MCP clients

Any client that accepts a streamable-HTTP MCP server works with the same config shape:

{
  "mcpServers": {
    "studiograph": {
      "type": "streamable-http",
      "url": "https://<your-workspace>/mcp",
      "headers": {
        "Authorization": "Bearer sg_your_token_here"
      }
    }
  }
}

This is exactly the snippet Studiograph hands you when you mint a token — with your workspace URL already filled in.

Local workspace (stdio)

If you run Studiograph locally, clients can spawn the CLI as a stdio MCP server instead of calling a URL:

{
  "mcpServers": {
    "studiograph": {
      "command": "studiograph",
      "args": ["mcp"],
      "cwd": "/absolute/path/to/your/workspace",
      "env": {
        "STUDIOGRAPH_MCP_TOKEN": "sg_your_token_here"
      }
    }
  }
}

studiograph mcp runs against the workspace in its working directory (or a path passed as an argument). When a local server is running for that workspace, it transparently proxies to it — so edits made over MCP merge live into any open editor. When no server is running, it falls back to operating on the workspace directly. Either way STUDIOGRAPH_MCP_TOKEN is required, and the same per-user folder access applies.

What connected tools can do

Around 53 tools are available, covering most of what you can do in the app:

Area	Tools cover
Search & read	Search across folders, list and read entries, find related entries, validate links
Entries	Create, update, patch, copy, move, and delete entries
Folders	Create folders and subfolders, archive folders — never permanent deletion
Datasets	Query data; add, insert, and delete rows and columns; set cells, filters, sorts, and formats
Artifacts	Create and edit artifacts frame by frame, inspect them, export them
Uploads	List library assets, attach them to entries, upload new files
History & restore	Browse file and folder history, list recent deletions, read past versions, restore
Comments	List comment threads on an entry, reply, resolve
Skills	List and load your saved workflow skills

Permanently deleting a folder is a human-only action in the web app; no MCP tool can do it.

Revoking access

Your minted tokens are listed under Settings → Agents → Advanced. Open a token and revoke it there; any client using it stops working immediately. The raw token value is never shown again after minting — if you lose it, revoke and mint a fresh one.

​Find your endpoint URL

​Mint a token (for headless clients)

​Claude Code

​Codex

​Claude Desktop and claude.ai

​Cursor and other MCP clients

​Local workspace (stdio)

​What connected tools can do

​Revoking access

Find your endpoint URL

Mint a token (for headless clients)

Claude Code

Codex

Claude Desktop and claude.ai

Cursor and other MCP clients

Local workspace (stdio)

What connected tools can do

Revoking access