In Windsurf's mcp_config.json add:
{
"mcpServers": {
"annsa": { "serverUrl": "https://app.annsa.ai/mcp" }
}
}
Reload MCP from Windsurf's settings panel.
01Add the server to mcp_config.json
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 are my top priorities?" · "Open the spec for the dark-mode request" · "Implement it — the spec lists the files to touch"
05Re-authenticating
Reload the server in Windsurf's MCP panel — an expired session reopens the browser consent screen.
06When it doesn't connect
Server not appearing: the key is serverUrl (not url) for remote servers in Windsurf's config.
"Not authenticated": reload the server and complete the browser consent.
"No priorities": import some feedback first.
07How do I add an MCP server to Windsurf?
Add the server under mcpServers in mcp_config.json with a serverUrl for remote servers — for Annsa, https://app.annsa.ai/mcp — then reload MCP from settings. First use opens a browser to authenticate; no local install is needed.
08Does Windsurf support remote MCP servers?
Yes — remote servers are configured with serverUrl in mcp_config.json and authenticate over OAuth in the browser. Remote means nothing to install and nothing to update locally; the server side carries the changes.