Circuitry MCP Server▌

by circuitry-dev
Connect AI coding agents to Circuitry’s visual workflow platform to convert flowcharts to code, sync project files, and
Connects AI coding agents to Circuitry's visual workflow platform, enabling them to create and sync code nodes from project files, understand user-drawn flowcharts and diagrams, generate visual flowcharts, and create data visualizations like spreadsheets and charts.
best for
- / Developers who prefer visual workflow representations
- / Teams documenting code architecture
- / Creating technical diagrams from existing codebases
capabilities
- / Create code nodes from project files
- / Sync code changes to visual workflows
- / Interpret user-drawn flowcharts and diagrams
- / Generate visual flowcharts from code
- / Create data visualizations and charts
- / Build interactive spreadsheets
what it does
Connects AI agents to Circuitry's visual workflow platform to create code nodes, interpret flowcharts, and generate visual diagrams from project files.
about
Circuitry MCP Server is an official MCP server published by circuitry-dev that provides AI assistants with tools and capabilities via the Model Context Protocol. Connect AI coding agents to Circuitry’s visual workflow platform to convert flowcharts to code, sync project files, and It is categorized under developer tools.
how to install
You can install Circuitry MCP Server in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Circuitry MCP Server is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
@circuitry/mcp-server
MCP (Model Context Protocol) server that gives AI coding agents access to Circuitry - a visual workflow and diagramming platform.
What It Does
- Visualize Code: Create code nodes from project files with bidirectional sync
- Understand Diagrams: AI agents can comprehend user-drawn flowcharts and diagrams
- Create Flowcharts: Generate visual flowcharts via Circuitry's chat agent
- Data Visualization: Create spreadsheets and charts from code analysis
Prerequisites
- Circuitry Server - Download from circuitry.dev/download
- Node.js 18+
- An MCP-compatible AI client (Claude Code, Cursor, VS Code, Gemini CLI, etc.)
Setup
1. Install & Configure Circuitry Server
- Download Circuitry Server from circuitry.dev/download
- Launch the app (appears in your system tray)
- Click the tray icon → Server → Preferences
- Click "Generate New Access Key"
- Copy the key — you'll need it in the next step
2. Run MCP Setup (Required)
npx @circuitry/mcp-server setup
This will prompt you to enter:
- EServer address — press Enter for default (
http://localhost:3030) - Access key — paste the key you generated above
This stores your credentials in ~/.circuitry/mcp-config.json.
3. Add to Your AI Client
Claude Code
claude mcp add circuitry npx @circuitry/mcp-server
Or manually add to ~/.claude/config.json:
{
"mcpServers": {
"circuitry": {
"command": "npx",
"args": ["-y", "@circuitry/mcp-server"]
}
}
}
Cursor
Settings → MCP → Add New MCP Server:
{
"mcpServers": {
"circuitry": {
"command": "npx",
"args": ["-y", "@circuitry/mcp-server"]
}
}
}
VS Code / Copilot
code --add-mcp '{"name":"circuitry","command":"npx","args":["-y","@circuitry/mcp-server"]}'
Gemini CLI
gemini mcp add circuitry npx @circuitry/mcp-server
Cline / Windsurf
Add to your MCP configuration using the standard format above.
4. Restart Your Client
Restart your AI client to load the MCP server.
Usage Examples
Visualize Code Files
You: Show me the auth files as code nodes in Circuitry
Agent: I'll create code nodes from your auth files...
Done! Created 4 code nodes:
- auth/login.ts
- auth/logout.ts
- auth/middleware.ts
- auth/types.ts
Changes sync bidirectionally with your source files.
Understand User-Drawn Flows
You: I've drawn a flow of how I think the auth should work
Agent: I'll analyze your flow in Circuitry...
I can see you've drawn a 5-node authentication flow:
1. Start → Login Form
2. Login Form → Validate Credentials
3. Validate Credentials → branches to Success/Failure
...
Create Flowcharts
You: Create a flowchart showing the error handling flow
Agent: I'll ask Circuitry's agent to create this flowchart...
Done! Created a flowchart with 7 nodes showing:
- Error detection
- Classification (runtime vs validation)
- Logging paths
- User notification
- Recovery options
Available Tools
Connection
| Tool | Description |
|---|---|
circuitry.status | Check connection status |
circuitry.connect | Request connection (shows permission dialog) |
Workflow Understanding
| Tool | Description |
|---|---|
workflow.getActive | Get current visible workflow info |
workflow.getStructure | Get simplified workflow structure |
workflow.resolveFlow | Resolve user reference ("this flow") to node IDs |
workflow.getNodeSummary | Get simplified node details |
Node Operations
| Tool | Description |
|---|---|
nodes.list | List all nodes in the workflow |
nodes.get | Get a node by ID |
nodes.update | Update node configuration |
nodes.delete | Delete a node |
Code Nodes
| Tool | Description |
|---|---|
code.create | Create code node (from file path with sync, OR with name+content) |
code.createBatch | Create multiple code nodes from files |
code.setCode | Update code content (syncs to source if applicable) |
Sheet Nodes
| Tool | Description |
|---|---|
sheet.create | Create a spreadsheet node with data |
sheet.setData | Replace sheet data |
Agent Delegation
| Tool | Description |
|---|---|
agent.chat | Send message to Circuitry's chat agent |
agent.createFlowchart | Ask agent to create a flowchart |
agent.poll | Poll for agent response (async) |
Configuration
Config File
Location: ~/.circuitry/mcp-config.json
{
"eserverUrl": "http://localhost:3030",
"accessKey": "your-key-here",
"configured": true
}
Environment Variables
| Variable | Description |
|---|---|
CIRCUITRY_ESERVER_URL | Override EServer URL |
CIRCUITRY_ACCESS_KEY | Override access key |
Commands
# Run setup wizard
npx @circuitry/mcp-server setup
# Check current configuration
npx @circuitry/mcp-server status
Troubleshooting
"Cannot connect to EServer"
- Check EServer is running: Look for the Circuitry icon in your system tray
- Start Circuitry Server: Download from circuitry.dev/download
- Verify URL: Run
npx @circuitry/mcp-server status
"Invalid access key"
- Create new key: Circuitry Server → Preferences → Generate New Access Key
- Re-run setup:
npx @circuitry/mcp-server setup
"No Circuitry browser client connected"
- Open Circuitry: Make sure the Circuitry app is open
- Refresh: Try refreshing the Circuitry page
Development
# Clone and install
git clone https://github.com/circuitry-dev/circuitry-mcp-server.git
cd circuitry-mcp-server
npm install
# Build
npm run build
# Test locally
npx tsx src/index.ts setup
npx tsx src/index.ts status
To test local changes, point your MCP config to the built output:
{
"mcpServers": {
"circuitry": {
"command": "node",
"args": ["/path/to/circuitry-mcp-server/dist/index.js"]
}
}
}
License
MIT
Links
FAQ
- What is the Circuitry MCP Server MCP server?
- Circuitry MCP Server is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Circuitry MCP Server?
- This profile displays 10 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Ratings
4.5★★★★★10 reviews- ★★★★★Shikha Mishra· Oct 10, 2024
Circuitry MCP Server is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Piyush G· Sep 9, 2024
We evaluated Circuitry MCP Server against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Useful MCP listing: Circuitry MCP Server is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Sakshi Patil· Jul 7, 2024
Circuitry MCP Server reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Ganesh Mohane· Jun 6, 2024
I recommend Circuitry MCP Server for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Oshnikdeep· May 5, 2024
Strong directory entry: Circuitry MCP Server surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Dhruvi Jain· Apr 4, 2024
Circuitry MCP Server has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Rahul Santra· Mar 3, 2024
According to our notes, Circuitry MCP Server benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Pratham Ware· Feb 2, 2024
We wired Circuitry MCP Server into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Yash Thakker· Jan 1, 2024
Circuitry MCP Server is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.