Appearance
MCP server
For AI tools that should look things up on their own, Protoki is also available as an MCP server — the same data, the same permission model, only a different protocol. The transport is Streamable HTTP, and the credential is the same API key as everywhere else.
json
{
"mcpServers": {
"protoki": {
"type": "http",
"url": "https://protoki.com/mcp",
"headers": { "Authorization": "Bearer pk_live_…" }
}
}
}Tools
| Tool | What it does | Scope |
|---|---|---|
search_meetings | With query, a full-text search across minutes, titles and transcripts. Without query, the most recent meetings — filterable by period, platform, status and company. | meetings:read |
get_protocol | The short version, the full text of the minutes, and the participants of one meeting. | meetings:read |
list_action_items | Tasks, optionally for one meeting. | action_items:read |
A personal key sees only its owner's meetings here too. There are deliberately no writing tools — a model should fetch data, not run up cost.
Signing in without a key (OAuth)
Clients such as claude.ai or Claude Desktop cannot store static headers. They connect to https://protoki.com/mcp as a custom connector, and registration, sign-in and consent run automatically: OAuth 2.1 with PKCE, read access only, on behalf of the person who signed in.
The entry points are published under /.well-known/oauth-protected-resource/mcp.