AI clients
Your AI assistant, working inside your workspace.
Papyro ships an MCP server, so Claude, Cursor or any MCP client can read and write your boards and notes — on your server, under your rules.
Works with the client you already use
A Streamable-HTTP MCP endpoint at /api/mcp. Point Claude, Cursor or any MCP-capable client at your own domain — there is no Papyro cloud in between.
Eleven tools, not a chat box
List and create boards, lists and cards, comment on a card, read and write notes, and list or mute error fingerprints. Real writes, scoped to what the caller is allowed to touch.
OAuth 2.1 or a scoped key
Your install is its own authorization server — dynamic client registration and PKCE, discoverable through the standard well-known documents. Prefer a token? A scoped papyro_ API key works too.
Every call on the record
The admin console lists each connection and each tool call, so you can see exactly what an assistant did and when — the same audit trail a human user gets.
One switch cuts everyone off
Turning MCP off rejects every token before any tool runs, for both auth modes. Existing keys and OAuth grants survive, so flipping it back restores access without re-consent.
Budgeted by design
Each connection runs under a usage budget, so a runaway agent burns its own allowance instead of your database.