Integrations
Every feedback source, one pipeline.
Connect where feedback lives, ground the build in your repository and carry the specification into your coding agent.
Product intelligence, wherever work happens.
Feedback in → Repository context → Specs out
Surveys
Slack
Intercom
Reddit
GitHub
Cursor
Claude Code
Codex
All integrations.
Every card leads to the integration detail: what it connects, how it works and how to set it up.
Feedback in · import
Repository context
Automation + API
One connected loop
Context survives every handoff.
01 · LISTEN
Signals arrive continuously or through deliberate imports.
02 · GROUND
GitHub adds the codebase context behind the decision.
03 · BUILD
Cursor and Claude Code receive the evidence with the spec.
Asked + answered.
Q1
How do I connect Annsa to Claude Code or Cursor?
Over MCP. In Claude Code, run: claude mcp add --transport http annsa https://app.annsa.ai/mcp. In Cursor, go to Settings, then MCP, then Add server, and paste https://app.annsa.ai/mcp. The first run opens your browser for OAuth on Annsa's consent screen.
Q2
Is there anything to install?
No. Annsa MCP is a remote server, so there is no package, no local process and no token file to manage. Re-authenticating is done from the client, not by deleting anything on disk.
Q3
Which coding and prototyping tools can read Annsa?
Claude Code, Cursor, Codex, ChatGPT, Windsurf, Figma Make, Lovable and Bolt. Each has its own connect page under docs. The agent gets 6 tools over one connection: annsa.priorities, annsa.spec, annsa.act, annsa.ask, annsa.surveys and annsa.help.
Q4
Do I need an integration before I can start?
No. You can upload a CSV or paste feedback in by hand and get ranked priorities from that alone. Integrations remove the copying, they are not a precondition.