In Bolt's connectors panel choose add custom MCP server and paste:
https://app.annsa.ai/mcp
First use opens the browser for OAuth on Annsa's consent screen.
01Add the custom MCP server
02Authenticate
The first use opens a browser on Annsa's consent screen — approve once and the six tools appear. There is no API key to paste and no token file to manage; access is your Annsa login, scoped to your workspace.
03The six tools
| Tool | What it does |
|---|---|
annsa.priorities | Ranked priorities with scores, volume, trend and shipping-history flags |
annsa.spec | Full spec for any priority, plus related context from past ships |
annsa.act | Build, ship, share, assign, correct, park, submit feedback or a transcript |
annsa.ask | Search feedback, priorities, specs and help articles |
annsa.surveys | How your in-product surveys are performing — each one with its instrument and results |
annsa.help | How Annsa itself works — product and how-to questions |
04Three things to ask first
"What should I build next?" · "Get the spec for the top priority" · "Scaffold it — the spec says what done looks like"
05Re-authenticating
Remove and re-add the server from the connectors panel — consent runs in the browser.
06When it doesn't connect
Tools not appearing: confirm the URL pasted exactly and the OAuth consent completed.
"No priorities": import some feedback into Annsa first.
07How do I add an MCP server to Bolt?
From the connectors panel, add a custom MCP server and paste the server URL — for Annsa, https://app.annsa.ai/mcp. Bolt opens a browser to authenticate on first use; after consent the server's tools are available in your session.
08Can Bolt generate an app from a product spec?
Connected to Annsa, yes — pull any priority's spec with annsa.spec and hand it to Bolt as the brief. It carries what to build, why it matters, customer quotes and done-when criteria, which is a stronger prompt than a one-line idea.