Developers
Annsa for developers
The MCP server, the REST API and every machine-readable surface, in one place. Nothing to install.
Connect over MCP
A remote server. Nothing to install.
claude mcp add --transport http annsa https://app.annsa.ai/mcp4 tools, one connection
What the agent gets once it is connected.
annsa.priorities
The ranked list, with the reasoning attached
annsa.spec
A full spec, grounded in the repo
annsa.act
Act on a priority — state, ownership, outcome
annsa.ask
Ask about the feedback, the surveys or Annsa itself, and fetch the skills an agent needs
Machine-readable surfaces
Every page on annsa.ai also has a markdown representation. Request any URL with an Accept header of text/markdown and you get the page as markdown rather than HTML.
OpenAPI 3.1 spec for the REST API. CORS-open.
MCP discovery document.
Server card (SEP-2127) — name, icon, description.
ARD catalog, spec 1.0.
How an agent authenticates, including what does not exist.
The site, summarized for a model.
The full reference, including every changelog entry.
The REST API is documented at /docs/api, and how an agent gets its own credential at /docs/agent-access.
Clients with a connect guide
Any MCP client can connect. These 8 have a page of their own.
Asked + answered.
Do I need to install anything?
Remote MCP at https://app.annsa.ai/mcp is the way to connect; there is nothing to install.
How does an agent authenticate?
OAuth 2.1 with PKCE S256. Access tokens last 30 days and refresh tokens 90. The first run opens a browser on Annsa's consent screen. Full detail, including what does not exist, is at /auth.md.
Can an agent have its own credential rather than a seat?
Yes. An agent can be minted a credential of its own, so every action it takes is signed with its name and traceable back to it. See /docs/agent-access.
Is the OpenAPI spec callable from a browser?
Yes. /openapi.json is CORS-open and linked from every page as rel=service-desc, so a tool can find it without being told where to look.