Integration · Briefs out

Claude Code, with your customer signal in reach.

One command and Claude Code can call four Circuit MCP tools — pull the spec, ask your feedback, act on it — all without leaving the terminal.

Claude Code reads Circuit specs live over MCP.

Install in Claude Code →See Ship →

— How it connects —

One line in the terminal.

Copy-paste from Circuit, authorise once, then use the tools in any conversation.

01

Run one command.

`claude mcp add circuit -- npx circuit-mcp`. One line, copy-pasted straight from Circuit.

02

Authorise via MCP OAuth.

PKCE S256, refresh tokens. The same auth path as Cursor — no API keys to paste or rotate.

03

Use the four MCP tools.

circuit.priorities, circuit.spec, circuit.act, circuit.ask — in any conversation. Two more in development.

04

Stay in the terminal.

Pull the spec, refine it, ship it — all without switching to the browser.

— What you get —

A workflow, not just a connection.

The four tools map to four jobs — fetch, read, act, search.

A real workflow in the CLI.

Ask “what’s my top priority?” in Claude Code; it calls circuit.priorities and shows you. Then circuit.spec to read it. Then circuit.act to ship when you’re done.

Feedback queries from the terminal.

circuit.ask runs semantic search across your signals, priorities, briefs and outcomes — without leaving Claude Code.

Works alongside Cursor.

Both connect over MCP — different clients, same Circuit endpoints. Use whichever fits the task in front of you.

— The proof —

Built on the official MCP CLI.

One-line install via the official Claude Code MCP CLI. PKCE S256, 30-day access token, 90-day refresh.

— Questions —

Asked and answered.

How do I install Circuit in Claude Code?

One command: claude mcp add circuit -- npx circuit-mcp. Authorise via MCP OAuth on first use.

What can Claude Code do with the connection?

Call four MCP tools — circuit.priorities, circuit.spec, circuit.act, circuit.ask. Each maps to a clear job: fetch, read, act, search.

Does this work alongside Cursor?

Yes. Both connect over MCP — different clients, same Circuit endpoints. Use whichever fits the task.

What scopes does it need?

Read pulls priorities, specs and feedback. Write enables ship, assign, park and submit. You choose which to grant.

Ship from the terminal. With every citation intact.

Install in Claude Code →See Ship →

— Related —

Cursor · GitHub · Linear · All integrations

Part of Circuit’s autonomous product intelligence stack — see the full picture.