SummitScribe

npx add-mcp 'https://summitscribe.app/api/mcp'

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.

You can also find SummitScribe in the Claude connectors directory, the MCP Registry, Glama and ClawHub.

Sign in or use a token

Apps that support MCP sign-in, such as ChatGPT, Claude and Grok Bot, need only the URL. They open SummitScribe in your browser, you sign in and choose which scopes to allow, and the app keeps the connection. Approval happens on summitscribe.app on the web, not in the mobile or desktop apps. A connection lasts up to 90 days, and you can disconnect any app in Account settings, then Developer & agents. Tools that only take a header, like the config files further down, use a token instead.

ChatGPT

ChatGPT adds custom MCP servers through developer mode, on the web.

1. In ChatGPT on the web, open Settings, then Apps & Connectors, then Advanced settings, and turn on Developer mode.
2. Back in Apps & Connectors, choose Create. Name it SummitScribe, set the MCP server URL to https://summitscribe.app/api/mcp, and pick OAuth for authentication.
3. Choose Create. ChatGPT opens SummitScribe so you can sign in and approve the scopes you want.
4. In a new chat, add SummitScribe from the tools menu and ask about your meetings.

Claude (claude.ai and Claude Desktop)

Claude adds remote servers as custom connectors. A connector you add on claude.ai also shows up in Claude Desktop, and the reverse.

1. In Claude, open Settings, then Connectors, and choose Add custom connector.
2. Name it SummitScribe and set the URL to https://summitscribe.app/api/mcp. Leave the advanced OAuth fields empty.
3. Choose Add, then Connect. Claude opens SummitScribe so you can sign in and approve the scopes you want.
4. In a chat, turn SummitScribe on from the tools menu.

Grok Bot

Grok Bot adds MCP servers from chat. Send your bot this message.

1. Add the MCP server https://summitscribe.app/api/mcp and name it SummitScribe. It signs in with OAuth, so no token is needed.
2. Confirm when the bot asks, then sign in to SummitScribe and approve the scopes you want when the sign-in card opens.

Make a token

1. Sign in at summitscribe.app on the web and open Account settings (from your profile menu), then Developer & agents.
2. 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.
3. 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. We email you whenever a token is created. If you think one leaked, revoke it in Developer & agents 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.