MCP server (Claude, Cursor & more)

Overview

POST /v1/mcp

The server speaks the Model Context Protocol (Streamable HTTP, JSON-RPC 2.0) and is stateless — no session, no OAuth. Authentication uses the same kuno_live_… key as the REST API. Which tools are visible depends on your key's scopes.

The four tools

Tool	Scope	What it returns
list_recordings	recordings.read	Your recordings, newest first (limit 1–50).
search_recordings	recordings.read	Title search across your recordings (query, limit).
get_recording	recordings.read	One recording in detail — with summaries.read also the summary + transcript, with actions.read the action items.
list_action_items	actions.read	Action items across all recordings (status filter, limit 1–100).

Connect with Claude

In Claude (web or desktop), go to Settings → Connectors → Add custom connector, enter the URL https://api.heykuno.com/v1/mcp and set your API key as the Bearer token. Claude can then answer things like "summarize my meetings from this week" straight from your Kuno notes.

Connect with Cursor

In Cursor, add the server to mcp.json:

{
  "mcpServers": {
    "kuno": {
      "url": "https://api.heykuno.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer kuno_live_your_key"
      }
    }
  }
}

Tip: The Kuno app shows a ready-made setup guide under Settings → Integrations → Claude / Cursor / MCP and creates the key for you.

Protocol details

• initialize returns server info (name "Kuno", version) and capabilities.
• tools/list only shows tools whose scope your key holds.
• tools/call runs a tool; scope errors come back as tool errors, not HTTP errors.
• Batch requests are not supported (JSON-RPC error −32600).
• GET /v1/mcp responds with 405 — the server is POST-only.