From deeplink to live spec.
cursor://anysphere.cursor-deeplink/mcp/install?name=circuit&config={b64} — the config block tells Cursor to run npx -y @anthropic-ai/mcp-remote https://app.withcircuit.com/mcp. Cursor handles the install.
PKCE S256, refresh tokens, 30-day access, 90-day refresh. Standard MCP 2.1.
circuit.priorities, circuit.spec, circuit.act, circuit.ask.
When you change the spec in Circuit, what the agent reads next changes. No paste.
Four tools, one live connection.
Fetch the ranked list, pull a full spec, ask questions of your feedback, act on it. Two more in development (circuit.refine, circuit.release).
The spec the agent reads is the current one — when the customer signal moves on, so does what gets built.
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.
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.
Asked and answered.
One click — the install deeplink (cursor://anysphere.cursor-deeplink/mcp/install?name=circuit&config={b64}) opens Cursor and handles the install. You authorise once via MCP OAuth, and the connection persists.
Four MCP tools: fetch ranked priorities, pull a full spec, ask semantic questions of your feedback, and act on it (ship, assign, park, submit).
Only with write scope. Read pulls priorities, specs and feedback; write enables ship, assign, park and submit. You decide which scope to grant.
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.
Part of Circuit’s autonomous product intelligence stack — see the full picture.