Connect Circuit to your stack
Every integration.
Eleven paths to get feedback into Circuit and specs out to where you build. Each one runs the same pipeline: classify, cluster, dedupe, attribute, rank.
Feedback
Don’t see your tool?
Request an integration.
Tell us where your feedback lives. We close the loop on feedback — including feedback about Circuit — so every request shapes what connects next. Until it lands, webhooks and the API wire in anything with an HTTP endpoint.
Coding
Cursor and Claude Code via MCP
Circuit is the feedback MCP for Cursor and Claude Code — the feedback to spec pipeline, delivered via the Model Context Protocol. Pull priorities, fetch specs, search feedback and take actions from inside your coding tool. Use circuit.act to mark as shipped, notify customers, submit feedback or submit a transcript. Ship from terminal.
Setup
- •Cursor: Add Circuit MCP to your Cursor config
- •Claude Code: Run
claude mcp add circuit - •First run opens a browser for OAuth authentication
- •Token cached locally for 30 days
4 MCP tools
circuit.prioritiesRanked priorities ready to buildcircuit.specFull spec for any priority with all 5 sectionscircuit.askSearch feedback and priorities for contextcircuit.actShip from terminal: mark shipped, notify customers, submit feedback or transcripts, assign, correct, parkContext
GitHub. Codebase comprehension for every spec
Connect your repo and Circuit reads the codebase to generate specs that reflect how your team builds — not just file paths, but what's inside them. Specs can only reference files that exist in your codebase. The system won't generate paths it hasn't seen. Circuit reads your .cursorrules and CLAUDE.md before generating, so the spec your coding tool receives already follows your team's rules. Create GitHub issues directly from any spec. The result is a codebase-aware product spec — not a generic template.
What Circuit reads
- File signatures — exports, types and key functions from relevant source files
- .cursorrules / CLAUDE.md — specs follow your team's coding rules
- Testing patterns — a sample test file so specs match your testing style
- Directory structure — compact file tree for accurate path suggestions
- Open issues — avoids duplicating existing tracked work
- Recent merged PRs — informs which files are suggested as relevant
- Tech stack — detected framework, language and environment
- CI/CD + config files — workflow names and config files present
- README — project overview when no AI config files exist
All read-only. Circuit never writes to your repository.
What specs include
Actual file paths marked as new or modify, coding conventions that follow your .cursorrules and CLAUDE.md rules, and a Heads Up section when similar open issues already exist in your repo.
As your team refines .cursorrules and CLAUDE.md over time, Circuit's specs improve automatically — both systems read from the same source of truth.
Automation
Webhooks. Connect anything else
Send events to any HTTP endpoint, Slack channel, Linear, GitHub or PagerDuty.
Available events
Test any hook before going live with full execution history, timestamps and status codes. All integrations included on every plan.
See pricing →Asked and answered.
How does Circuit connect to Slack?
Q1Add the Circuit Slack integration. Circuit polls your selected channels every 10 minutes, classifies each message by intent, urgency and sentiment, and feeds it into the priority pipeline. No manual sorting.
How do MCP tools work in Cursor and Claude Code?
Q2Install circuit-mcp from npm. Four tools: circuit.priorities (ranked list), circuit.spec (full spec with file paths), circuit.act (ship, assign, correct) and circuit.ask (search feedback). Specs arrive where code gets written.
What feedback sources does Circuit support?
Q3Circuit Surfaces (embed on any site), Slack, Google Sheets, CSV, transcripts (Otter, Fireflies, Grain, Whisper), Reddit, in-product surveys, manual entry and the API. All feed the same pipeline.
Does Circuit replace my existing tools?
Q4No. Circuit reads from Slack, spreadsheets and support threads — wherever feedback already lives. It adds the layer that was missing: scored priorities and codebase-grounded specs.