annsa
Log inStart free

Integration · Briefs out

Cursor pulls the live spec.

Install Annsa in Cursor with a deeplink. The agent calls four MCP tools — pull the spec, ask your feedback, act on it — without leaving the editor.

Start freeSee Ship →

How it connects

From deeplink to live spec.

Cursor reads Annsa specs live over MCP.

01
Click the deeplink.

One click opens Cursor and starts the install.

02
Authorise via MCP OAuth.

PKCE S256, refresh tokens, 30-day access, 90-day refresh. Standard MCP 2.1.

03
The agent gets four MCP tools.

annsa.priorities, annsa.spec, annsa.act, annsa.ask.

04
Build from the live spec.

When you change the spec in Annsa, what the agent reads next changes. No paste.

What you get

Four tools, one live connection.

Four MCP tools, one connection.

Fetch the ranked list, pull a full spec, ask questions of your feedback, act on it — four tools over one connection.

Live, not pasted.

The spec the agent reads is the current one — when the customer signal moves on, so does what gets built.

Repo conventions travel with the spec.

When GitHub is connected, the Files-to-Touch section carries the actual paths, related issues, conventions (CLAUDE.md, .cursorrules) and a sample test — Cursor builds against your standards.

The proof

Built on standard MCP.

PKCE S256, 30-day access token, 90-day refresh. Five-minute in-memory token cache avoids DB round-trips per call.

MCP · OAuth 2.1
Cursor requests the live Annsa spec
PKCE S256live specrepo context
agent ready

Asked + answered.

Q1
How do I install Annsa in Cursor?
One click — the install deeplink opens Cursor and handles the install. You authorise once via MCP OAuth, and the connection persists.
Q2
What can the agent do?
Four MCP tools: fetch ranked priorities, pull a full spec, ask semantic questions of your feedback, and act on it (ship, assign, park, submit).
Q3
Can the agent change my data?
Only with write scope. Read pulls priorities, specs and feedback; write enables ship, assign, park and submit. You decide which scope to grant.
Q4
How are tokens managed?
MCP OAuth 2.1 — PKCE S256, refresh tokens. Tokens cached in memory for five minutes to avoid DB round-trips per call; per-user rate-limited to prevent credit-burn.

More integrations

annsa

Build from what’s true now.

The spec the agent reads is always the current one — no copy-paste.

Start freeSee Ship →