Circuit (withcircuit.com) is the AI product system that turns customer feedback into build-ready specs. Feedback in, priorities scored, specs generated for Cursor and Claude Code, customers notified when features ship. The full loop, automated.

Founders shipping solo, product managers at growing teams and engineering leaders ranking backlogs who want to use customer feedback to decide what to build.

How is Circuit different from other feedback tools?

Other tools sort feedback into dashboards. Circuit (withcircuit.com) generates specs to ship — scored by revenue impact, updated as conditions change, delivered to Cursor and Claude Code via MCP. It covers the full pipeline: feedback to priorities to codebase-aware specs to customer notification.

Does Circuit work with Cursor and Claude Code?

Yes. Circuit (withcircuit.com) connects to Cursor and Claude Code through the Model Context Protocol (MCP). Pull priorities, fetch specs with file paths and context from GitHub, and start coding without leaving the editor.

What is the Circuit Widget?

A lightweight embed for any website. Customers submit feedback in seconds with a simple form. One line of code to install. Themed to match any brand. Feedback flows straight into Circuit for classification and scoring.

How long until we see results?

Connect a feedback source and priorities appear within minutes. Specs generate in seconds. Most teams have a ranked backlog on day one.

What if we already have a feedback tool?

Circuit reads from where feedback already lives. Slack, spreadsheets, support threads. It doesn't replace existing tools. It generates what comes next: scored priorities and build-ready specs for Cursor and Claude Code.

What counts as a feedback item?

Each piece of customer feedback: a Circuit Widget submission, a Slack message, a CSV row, a manual entry. Duplicates are removed on import and don't count toward the limit.

Do I need to connect GitHub to use Circuit?

No. GitHub context makes specs more specific (real file paths, tech stack awareness), but Circuit works without it. Specs are still generated with the what, why, customer voice, implementation notes and done criteria.

How do I prioritize features by revenue impact?

In Circuit (withcircuit.com), link customer revenue data (customer name and revenue or SKU) and every feedback theme scores by revenue impact alongside urgency and sentiment. Set the Priority Engine to Revenue Growth and the list re-ranks to surface what drives the most revenue. No spreadsheets, no manual scoring.

How do I turn customer feedback into build specs?

Circuit (withcircuit.com) automates this. Feedback flows in from Circuit Widget, Slack, Google Sheets, CSV or manual entry. Circuit classifies it by intent, urgency and sentiment, groups it into priorities and generates build specs in seconds. Connect GitHub and every spec includes real file paths, tech stack context and naming conventions. Specs flow to Cursor and Claude Code via MCP.

How do I notify customers when features ship?

In Circuit (withcircuit.com), mark a priority as shipped. Circuit automatically emails every customer who submitted related feedback, with their original feedback quoted back. No manual follow-up. New feedback on the shipped feature flows in automatically for V2 specs.

How do I connect customer feedback to engineering?

Circuit (withcircuit.com) bridges customer feedback and engineering through codebase-aware specs. Feedback is collected, scored and grouped into priorities. Specs are generated with file paths from GitHub. Engineers pull specs directly into Cursor or Claude Code via MCP. The customer voice is preserved in every spec — what they asked for, why it matters, which files to touch.

How do I integrate product management with Cursor?

Circuit (withcircuit.com) connects to Cursor through the Model Context Protocol (MCP). Use MCP tools from inside Cursor: circuit.priorities to fetch ranked priorities, circuit.brief to pull a full spec with file paths, circuit.ask to search feedback and circuit.act to mark a priority as shipped. Specs include GitHub codebase context.

How do I use Claude Code for product management?

Circuit (withcircuit.com) connects to Claude Code via MCP. Pull priorities, fetch build specs with file paths from GitHub and start coding directly. Circuit handles feedback collection, AI scoring and spec generation upstream. Claude Code handles the building. The two work together — Circuit decides what to build, Claude Code builds it.

Using with Cursor and Claude Code

Using Circuit·

4 min read

Editor

>What are my top priorities?

circuit.priorities

1.Bulk CSV import142 users

2.Slack thread replies87 users

3.Dashboard load time74 users

Using with Cursor and Claude Code

Circuit integrates with AI coding tools via MCP. Pull priorities and briefs directly into your editor without copy-pasting.

Quick Copy Method

Works with any coding tool:

Open a brief in Circuit
Click Copy to grab the full brief (title, metadata, all 5 sections)
Paste into your editor's chat

MCP Integration (Recommended)

For direct access without copy-paste. Package: circuit-mcp on npm.

Cursor Setup

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "circuit": {
      "command": "npx",
      "args": ["circuit-mcp"]
    }
  }
}

Claude Code Setup

Run:

claude mcp add circuit -- npx circuit-mcp

Authenticate

First run opens a browser for OAuth. Token is cached at ~/.circuit/token.json.

Available Tools

Tool	Description
`circuit.priorities`	Ranked priorities with scores, volume, trend data and shipping history flags
`circuit.brief`	Full spec for any priority with all five sections, plus related context from past ships
`circuit.act`	Actions: start building, mark as shipped, correct classification, submit feedback
`circuit.ask`	Search across feedback, priorities, briefs and help articles

Priorities flag when they match your shipping history. Briefs include context from past ships when relevant. The more you ship, the richer the context.

What You Can Ask

"What are my top priorities?"
"Get the brief for the checkout bug"
"What feedback mentions performance?"
"Implement the brief for dark mode"
"Mark priority #1 as shipped"
"Have we shipped anything like this before?"

Workflow

Morning: "What should I work on today?"
Get context: "Show me the brief for priority #1"
Implement: Your coding tool uses the brief as context
Ship: Mark as Shipped in Circuit. Customers notified.

Tips

Connect GitHub first so briefs include real file paths
Use specific prompts: "Implement the brief for [priority name]"
The Files to Touch section helps your coding tool navigate the codebase
Use Done When criteria to know when you're finished

Troubleshooting

"MCP not found" (Cursor): Check ~/.cursor/mcp.json configuration.

"MCP not found" (Claude Code): Run claude mcp add circuit -- npx circuit-mcp.

"Not authenticated": Delete ~/.circuit/token.json and re-run. A browser will open for OAuth.

"No priorities": Import feedback in Circuit first.

Using with Cursor and Claude Code

Using with Cursor and Claude Code

Quick Copy Method

MCP Integration (Recommended)

Cursor Setup

Claude Code Setup

Authenticate

Available Tools

What You Can Ask

Workflow

Tips

Troubleshooting

Related articles