Connect InnerSheet to your AI client

One command from your terminal. Export the environment variable first, or pass it with -e:

claude mcp add innersheet   -e GOOGLE_OAUTH_CLIENT_SECRETS=/path/to/client_secret.json   -- /path/to/innersheet/.venv/bin/python /path/to/innersheet/server.py

• Check it with claude mcp list.
• For a project the whole team shares, commit a .mcp.json file with the same mcpServers block as Claude Desktop — teammates only need their own client_secret.json.
• InnerSheet also ships as a Claude Code plugin bundle (skill + hooks); see the Tools page for what the plugin adds.

Create .cursor/mcp.json in your project (or Cursor → Settings → MCP → Add):

{
  "mcpServers": {
    "innersheet": {
      "command": "/path/to/innersheet/.venv/bin/python",
      "args": ["/path/to/innersheet/server.py"],
      "env": {
        "GOOGLE_OAUTH_CLIENT_SECRETS": "/path/to/client_secret.json"
      }
    }
  }
}

Cursor also imports Claude Code hooks from ~/.claude/settings.json when Third-Party Imports is on (it is by default), so the InnerSheet safety hooks work in Cursor without extra configuration.

Add this to ~/.codex/config.toml (or run codex mcp add). Watch the table name — it is snake_case mcp_servers, not mcpServers; a typo means the section is silently ignored.

[mcp_servers.innersheet]
command = "/path/to/innersheet/.venv/bin/python"
args = ["/path/to/innersheet/server.py"]

[mcp_servers.innersheet.env]
GOOGLE_OAUTH_CLIENT_SECRETS = "/path/to/client_secret.json"

Verify with codex mcp list, then type /mcp inside Codex to see the server and its tools. A project can scope the same table in .codex/config.toml, which Codex only reads for trusted projects.

Preferred: the portable .mcp.json at the workspace root, which uses the top-level key mcpServers. The older .vscode/mcp.json uses servers instead — copying an entry between the two files without renaming the key is the most common silent failure.

{
  "mcpServers": {
    "innersheet": {
      "command": "/path/to/innersheet/.venv/bin/python",
      "args": ["/path/to/innersheet/server.py"],
      "env": {
        "GOOGLE_OAUTH_CLIENT_SECRETS": "/path/to/client_secret.json"
      }
    }
  }
}

Then switch Copilot Chat to Agent mode — MCP tools do not run in Ask mode. The Copilot CLI reads the same entry from ~/.copilot/mcp-config.json. If Copilot comes from an organisation, the "MCP servers in Copilot" policy must be enabled by an admin, and it is disabled by default.

One command (-s user makes it available everywhere), or edit ~/.gemini/settings.json by hand:

gemini mcp add -s user innersheet   -e GOOGLE_OAUTH_CLIENT_SECRETS=/path/to/client_secret.json   /path/to/innersheet/.venv/bin/python /path/to/innersheet/server.py

Restart gemini and run /mcp — InnerSheet should show as CONNECTED with its tools listed underneath. Note that Gemini CLI access for free and individual paid accounts moved to the Antigravity CLI in June 2026, so check which CLI your plan uses before setting this up.