by circuitry-dev
Connect AI coding agents to Circuitry’s visual workflow platform to convert flowcharts to code, sync project files, and
Connects AI agents to Circuitry's visual workflow platform to create code nodes, interpret flowcharts, and generate visual diagrams from project files.
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.
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.
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.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
I recommend Circuitry MCP Server for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Circuitry MCP Server surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Circuitry MCP Server is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Circuitry MCP Server reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Circuitry MCP Server is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
I recommend Circuitry MCP Server for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Circuitry MCP Server has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Circuitry MCP Server is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Circuitry MCP Server reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Useful MCP listing: Circuitry MCP Server is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 66
MCP (Model Context Protocol) server that gives AI coding agents access to Circuitry - a visual workflow and diagramming platform.
npx @circuitry/mcp-server setup
This will prompt you to enter:
http://localhost:3030)This stores your credentials in ~/.circuitry/mcp-config.json.
claude mcp add circuitry npx @circuitry/mcp-server
Or manually add to ~/.claude/config.json:
{
"mcpServers": {
"circuitry": {
"command": "npx",
"args": ["-y", "@circuitry/mcp-server"]
}
}
}
Settings → MCP → Add New MCP Server:
{
"mcpServers": {
"circuitry": {
"command": "npx",
"args": ["-y", "@circuitry/mcp-server"]
}
}
}
code --add-mcp '{"name":"circuitry","command":"npx","args":["-y","@circuitry/mcp-server"]}'
gemini mcp add circuitry npx @circuitry/mcp-server
Add to your MCP configuration using the standard format above.
Restart your AI client to load the MCP server.
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.
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
...
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
| Tool | Description |
|---|---|
circuitry.status | Check connection status |
circuitry.connect | Request connection (shows permission dialog) |
| 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 |
| 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 |
| 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) |
| Tool | Description |
|---|---|
sheet.create | Create a spreadsheet node with data |
sheet.setData | Replace sheet data |
| 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) |
Location: ~/.circuitry/mcp-config.json
{
"eserverUrl": "http://localhost:3030",
"accessKey": "your-key-here",
"configured": true
}
| Variable | Description |
|---|---|
CIRCUITRY_ESERVER_URL | Override EServer URL |
CIRCUITRY_ACCESS_KEY | Override access key |
# Run setup wizard
npx @circuitry/mcp-server setup
# Check current configuration
npx @circuitry/mcp-server status
npx @circuitry/mcp-server statusnpx @circuitry/mcp-server setup# 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"]
}
}
}
MIT
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.