~ open-source · mcp-native · local-first
Local-first visual MCP workflow builder for Claude.
Run Torqa locally, connect it to Claude as an MCP server, and turn plain-English automation requests into visual workflow plans with tools, approvals, safety notes, and exportable JSON.
- Open source
- Runs locally
- MCP server
- Planning today
- Execution planned
claude prompt
› “Create a workflow that reads urgent Gmail emails, notifies Slack, and drafts replies.”
01 · prompt
Prompt
Claude / user
02 · server
Torqa MCP Server
stdio · local
03 · plan
Workflow Plan
tools · steps · approvals
04 · graph
Visual Graph
nodes + edges
05 · export
JSON Export
torqa.workflow.v1
# what it does
Workflow planning, not workflow execution.
# how it works
Four steps from prompt to plan.
01
Clone and run locally
git clone, npm install, npm run mcp:server.
02
Add to Claude MCP config
Drop the torqa entry into claude_desktop_config.json.
03
Ask Claude for a workflow
Describe the automation in plain English.
04
Inspect and export
Open /builder, review the graph, copy the JSON.
# architecture
One process, one transport.
Claude / MCP Client
│ stdio
▼
Torqa MCP Server
│
▼
Workflow Planning Engine
│
▼
Visual Graph + JSON Export# shipped
What works today
- + Local MCP stdio server
- + 5 MCP workflow tools
- + Deterministic workflow planner
- + Visual builder (/builder)
- + JSON + Claude prompt export
- + mcp:smoke verification
# planned
Roadmap
- ~ Live external execution
- ~ OAuth + live tool introspection
- ~ Execution adapters (Gmail, Slack, …)
- ~ n8n-style import/export adapters
# quickstart
Clone, install, run.
$ git clone https://github.com/kadireren7/Torqa.git $ cd Torqa/dashboard $ npm install $ npm run mcp:server -- --help $ npm run mcp:smoke $ npm run dev
No environment variables. No database. No accounts.