Integration · Briefs out
Claude Code, with your customer signal in reach.
One command and Claude Code can call four Annsa MCP tools — pull the spec, ask your feedback, act on it — all without leaving the terminal.
How it connects
One line in the terminal.
Copy-paste from Annsa, authorise once, then use the tools in any conversation.
`claude mcp add --transport http annsa https://app.annsa.ai/mcp`. One line, copy-pasted straight from Annsa.
PKCE S256, refresh tokens. The same auth path as Cursor — no API keys to paste or rotate.
annsa.priorities, annsa.spec, annsa.act, annsa.ask — in any conversation.
Pull the spec, refine it, ship it — all without switching to the browser.
What you get
A workflow, not just a connection.
Ask “what’s my top priority?” in Claude Code; it calls annsa.priorities and shows you. Then annsa.spec to read it. Then annsa.act to ship when you’re done.
annsa.ask runs semantic search across your signals, priorities, briefs and outcomes — without leaving Claude Code.
Both connect over MCP — different clients, same Annsa endpoints. Use whichever fits the task in front of you.
The proof
Built on the official MCP CLI.
One-line install via the official Claude Code MCP CLI. PKCE S256, 30-day access token, 90-day refresh.
Asked + answered.
More integrations
Ship from the terminal. With every citation intact.
Four MCP tools in the terminal — pull priorities, read the spec, ship, ask.