@scriben/mcp

Your meetings, in any AI assistant.

Scriben records and understands your meetings. This is the MCP server that connects that memory to the assistant you already use, so it answers from what was actually said — not from what you remembered to paste in.

npx @scriben/mcp install

Requires Node 20+. macOS, Linux and Windows.

Setup

1. Run the command. It prints a short code and opens your browser.
2. Approve the device. Sign in, then type the code from your terminal. The code is what proves it was you who asked — not a page that happened to open.
3. Restart your assistant.

The installer writes the config for every client it finds:

| Client | Config | Written for you | |---|---|---| | Claude Desktop | claude_desktop_config.json | yes | | Claude Code | ~/.claude.json | yes | | Cursor | ~/.cursor/mcp.json | yes | | Windsurf | ~/.codeium/windsurf/mcp_config.json | yes | | VS Code | …/Code/User/mcp.json | yes | | Zed | ~/.config/zed/settings.json | yes | | Codex CLI | ~/.codex/config.toml | printed to paste — Codex uses TOML |

Tools

| Tool | Returns | |---|---| | list_notes | Recent meetings, newest first | | get_summary | What a meeting covered and decided | | get_action_items | Commitments, and who owns them | | get_context | What you know about a person | | recall_memory | Facts carried across meetings | | search_transcript | Where something was said |

Every response carries the note and date it came from, so your assistant can say "according to your note from Tuesday" rather than asserting a fact from nowhere.

What this deliberately cannot do

• Read-only. Nothing can be created, edited or deleted through this connection. There is no write path in the server.
• Summaries, not raw audio. Recordings never leave Scriben.
• No token in your config. Client configs are pasted into GitHub issues and screenshots all the time. Yours holds only a path; the credential lives in ~/.scriben/mcp.json, owner-readable only.
• No silent upgrades. The config pins an exact version. An unpinned spec would fetch and run new code on every launch without you agreeing to it.

Commands

npx @scriben/mcp install     # connect this machine and configure your clients
npx @scriben/mcp status      # show the current connection
npx @scriben/mcp uninstall   # revoke this device, then remove it from your clients

uninstall revokes on the server first and reports loudly if that fails — removing the local config first would leave you believing you had disconnected while a live credential stayed valid.

Options

| Flag | Meaning | |---|---| | --base-url <url> | Scriben server (default https://demo.scriben.ai) | | --credentials <path> | Where to keep the credential file | | --all | Write configs for every supported client, installed or not |

Revoking

From the Scriben app: Integrations → Scriben MCP. Access ends on the next request. Device credentials expire after 90 days regardless.

Links

• mcp.scriben.ai — setup guide
• home.scriben.ai — Scriben

MIT © Scriben