Use SummitScribe from your AI agent

Your agent can read your meeting notes, transcripts and action items through SummitScribe’s remote MCP server at https://summitscribe.app/api/mcp. Every tool is read-only. See the MCP reference for tools, scopes and limits.

Make a token

Sign in at summitscribe.app on the web and open Account settings (from your profile menu), then Developer & agents.
Create a token with mcp:read and the data scopes you want. Use one token per tool so you can revoke one without breaking the others.
Keep it in your tool’s secret prompt or in the SUMMITSCRIBE_TOKEN environment variable. Don’t paste it into a chat or commit it. If you think it leaked, revoke it in Settings right away.

Plugins

Claude Code, Cursor and Gemini CLI can install SummitScribe as a plugin from timmyk31/summitscribe-agents. The Claude Code plugin asks for your token and keeps it in secure storage. Gemini CLI opens your browser so you can approve the connection, with no token.

# Claude Code
/plugin marketplace add timmyk31/summitscribe-agents
/plugin install summitscribe@summitscribe

# Gemini CLI
gemini extensions install https://github.com/timmyk31/summitscribe-agents

Claude Code

Run this once in your terminal, with your token in SUMMITSCRIBE_TOKEN. Your shell expands the variable when you run it, so Claude Code saves the token itself in plain text in ~/.claude.json. Keep that file private, or use the plugin once it is listed.

claude mcp add --transport http summitscribe https://summitscribe.app/api/mcp \
  --header "Authorization: Bearer $SUMMITSCRIBE_TOKEN"

Cursor

Add this to your global or project MCP file. Cursor reads the token from your environment. File: ~/.cursor/mcp.json.

{
  "mcpServers": {
    "summitscribe": {
      "url": "https://summitscribe.app/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:SUMMITSCRIBE_TOKEN}"
      }
    }
  }
}

VS Code (Copilot agent mode)

VS Code asks for the token the first time and keeps it in its secret storage. File: .vscode/mcp.json.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "summitscribe-token",
      "description": "SummitScribe token",
      "password": true
    }
  ],
  "servers": {
    "summitscribe": {
      "type": "http",
      "url": "https://summitscribe.app/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:summitscribe-token}"
      }
    }
  }
}

Codex CLI

Codex sends the token from SUMMITSCRIBE_TOKEN as a bearer header. Export SUMMITSCRIBE_TOKEN in the shell before you start Codex. File: ~/.codex/config.toml.

[mcp_servers.summitscribe]
url = "https://summitscribe.app/api/mcp"
bearer_token_env_var = "SUMMITSCRIBE_TOKEN"

Gemini CLI

Gemini expands SUMMITSCRIBE_TOKEN from your environment. File: ~/.gemini/settings.json.

{
  "mcpServers": {
    "summitscribe": {
      "httpUrl": "https://summitscribe.app/api/mcp",
      "headers": {
        "Authorization": "Bearer ${SUMMITSCRIBE_TOKEN}"
      }
    }
  }
}

OpenClaw

Add the server under the top-level mcp.servers, with SUMMITSCRIBE_TOKEN set in your environment. On a paired headless node host (openclaw node run), the same entry goes under nodeHost.mcp.servers instead. Then install the SummitScribe skill from ClawHub when it is listed. File: ~/.openclaw/openclaw.json.

{
  "mcp": {
    "servers": {
      "summitscribe": {
        "url": "https://summitscribe.app/api/mcp",
        "transport": "streamable-http",
        "headers": {
          "Authorization": "Bearer ${SUMMITSCRIBE_TOKEN}"
        }
      }
    }
  }
}

Hermes Agent

Add the server under mcp_servers, and put SUMMITSCRIBE_TOKEN=your token in ~/.hermes/.env (or your environment). Hermes fills in ${SUMMITSCRIBE_TOKEN} from there. File: ~/.hermes/config.yaml.

mcp_servers:
  summitscribe:
    url: "https://summitscribe.app/api/mcp"
    headers:
      Authorization: "Bearer ${SUMMITSCRIBE_TOKEN}"

Meta Muse

Muse has no MCP settings screen. Send it this message in chat. When it asks for the token, paste it only into Muse’s secure credential prompt, never into the chat.

Create a custom connector named SummitScribe. Transport: Streamable HTTP. URL: https://summitscribe.app/api/mcp. It needs a bearer token; ask me for it with the secure credential prompt.

Your data

When your agent calls a tool, the meeting content it reads goes to that agent’s vendor under that vendor’s terms. SummitScribe never sends data anywhere you didn’t connect. See the privacy policy. Questions? Email info@summitscribe.app.