MCP server
The Saykeeper MCP server lets AI assistants list, search and read your meetings and ask questions about them. It uses the same API key as the API and is read only.
Server
https://api.saykeeper.com/v1/mcpStreamable HTTP, JSON-RPC 2.0. Send the key as Authorization: Bearer ntb_live_....
Tools
| Tool | What it does |
|---|---|
list_meetings | Recent meetings (default 20, max 100). |
get_meeting | One meeting with its transcript, paged by character offset. |
search_meetings | Search titles and transcripts (default 20, max 50). |
ask_meeting | Ask a question about one meeting; answered by AI over its transcript. |
ask_meetings | Ask a question across your meetings. |
The ask tools are limited to 20 questions per minute.
Connect a client
Replace ntb_live_YOUR_KEY with your key.
Claude Code
Run in a terminal:
claude mcp add --transport http saykeeper https://api.saykeeper.com/v1/mcp \
--header "Authorization: Bearer ntb_live_YOUR_KEY"Claude Desktop
Settings, Developer, Edit config. Paste into claude_desktop_config.json and restart Claude. Needs Node.js (npx runs mcp-remote, which forwards the header).
{
"mcpServers": {
"saykeeper": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.saykeeper.com/v1/mcp",
"--header",
"Authorization:${SAYKEEPER_AUTH}"
],
"env": {
"SAYKEEPER_AUTH": "Bearer ntb_live_YOUR_KEY"
}
}
}
}Cursor
Cursor Settings, MCP, Add new MCP server, or paste into ~/.cursor/mcp.json:
{
"mcpServers": {
"saykeeper": {
"url": "https://api.saykeeper.com/v1/mcp",
"headers": {
"Authorization": "Bearer ntb_live_YOUR_KEY"
}
}
}
}ChatGPT and Claude.ai
ChatGPT connectors and custom connectors in Claude.ai (the web app) sign in with OAuth or without sign-in, they cannot send an API key header, and the Saykeeper MCP server does not offer OAuth yet. Claude Code and Claude Desktop work with the key as shown above. In ChatGPT or Claude.ai use the prompt for AI with the API, for example in a custom GPT action with API key authentication of type Bearer.