MCP server for product management
The short answer
An MCP server for product management gives your coding agents a live line into the work: the ranked list, the specs, who asked and what is decided. Annsa is the source of direction for your agents, and its MCP server is how they connect. Claude Code, Cursor, Codex and Grok use one URL and eight tools to read, claim, file, ask and ship.
MCP (Model Context Protocol) is an open protocol from Anthropic that lets an AI tool call outside tools and read outside data.
TL;DR
- A product-management MCP server lets agents read the plan directly, so nobody pastes tickets into prompts.
- Check that agents can read, claim, file, ask and ship, and that you stay in charge of customer-facing actions.
- Annsa's server is remote at one URL: nothing to install, one browser sign-in.
When to use it: when agents need to know what to work on without asking you, or when more than one agent builds. When not: skip it if one agent works from a single short plan you already keep in a rules file.
What does an MCP server do for product work?
A product-management MCP server uses MCP so your agents read your plan directly. Nobody copies a ticket into a prompt, and the agent reads the live list, not a pasted copy.
Two things change. The agent can find out what to work on without asking you. And what it learns goes back to the same place instead of ending with the session.
What should a product-management MCP server let agents do?
Whatever server you pick, check that your agents can do these six things:
- Read the ranked list and the specs. What is next, why, and what done means.
- Claim work. So the list shows who holds what and two agents do not start the same job.
- File findings. A bug or idea the agent found goes on the list, not into a chat.
- Ask a person. A real question reaches you in a few lines, and the answer is saved.
- Ship with receipts. The agent checks each Done When line and records how.
- Keep the person in charge. Some actions, like emailing customers, should stay a person's call.
Also check how it signs in. A browser sign-in with OAuth beats a token in a config file.
How do I connect Claude Code, Cursor, Codex and Grok?
Annsa is a remote server at https://app.annsa.ai/mcp. There is nothing to install. The first run opens a browser for sign-in.
Claude Code
claude mcp add --transport http annsa https://app.annsa.ai/mcp
Codex (starts the browser sign-in itself; if it doesn't, run the second command)
codex mcp add annsa --url https://app.annsa.ai/mcp
codex mcp login annsa
Grok
grok mcp add --transport http annsa https://app.annsa.ai/mcp
Cursor has a one-click install in the Annsa docs. Or go to Settings, then MCP, then Add server, and paste https://app.annsa.ai/mcp.
Each agent keeps its own connection and reads the same priorities, specs and decisions. Full steps: Connect your agent.
What are Annsa's eight tools?
Three read and change nothing:
annsa.priorities: see what to work on next, ranked, with the evidence behind itannsa.spec: read the plan for one priority: what to build, why, and Done Whenannsa.ask: ask about your customers, your work or Annsa itself
Five write:
annsa.work: do the work on a priority, and settle routine asks with undoannsa.file: add what a customer said, what an agent found, or a new ideaannsa.decide: record a decision: your answer, a spec edit, or a ruleannsa.board: arrange the board. A merge retires numbers for goodannsa.share: tell the customers who asked that it shipped. Emails can't be unsent
Which should I let run? Let annsa.work and annsa.file run without asking. Approve annsa.decide, annsa.board and annsa.share each time, because they change what you decided or what your customers hear.
How does Annsa keep me in charge?
Annsa is AI agent management: choose what to build, direct your agents and learn as you go. The MCP server is how the "direct" part reaches Claude Code, Cursor, Codex and Grok.
- One agent holds each priority at a time, so agents do not collide.
- There are two paths to shipped. Your agent can mark a priority shipped; any Done When line it couldn't check is labeled on the spec, and that's your call. A merged pull request that names the priority ships it automatically only when it reaches your live branch and every Done When line has a receipt; otherwise it's held with a note.
- Signed in through the browser, an agent acts as you, so set your editor to ask before the three tools that change what you decided or what customers hear. With an agent credential, person-only actions, including sharing with customers, are refused.
- A person makes the call. Annsa drafts the customer notes; you review and send them.
See Tools and actions, Hand work to any agent and Direct your agents.