Integration · Briefs out
Claude Code, with your customer signal in reach.
One command and Claude Code can call six Annsa MCP tools — pull the spec, ask your feedback, act on it — all without leaving the terminal.
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.
How it connects
One line in the terminal.
Copy-paste from Annsa, authorize once, then use the tools in any conversation.
Run one command.
`claude mcp add --transport http annsa https://app.annsa.ai/mcp`. One line, copy-pasted straight from Annsa.
Authorize via MCP OAuth.
PKCE S256, refresh tokens. The same auth path as Cursor — no API keys to paste or rotate.
Use the six MCP tools.
annsa.priorities, annsa.spec, annsa.act, annsa.ask — in any conversation.
Stay in the terminal.
Pull the spec, refine it, ship it — all without switching to the browser.
What you get
A workflow, not just a connection.
A real workflow in the CLI.
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.
Feedback queries from the terminal.
annsa.ask runs semantic search across your signals, priorities, briefs and outcomes — without leaving Claude Code.
Works alongside Cursor.
Both connect over MCP — different clients, same Annsa endpoints. Use whichever fits the task in front of you.