n8n MCP
n8n MCP server that gives AI assistants access to n8n node documentation, properties, operations, and workflow automation context.Read full description
czlonkowskiLABSCO SUMMARY
Deploy the flow first, or it will not show up.
The tool surface is generated from your own account, which is the point and also the catch: nothing appears until an app is deployed from the Wordware editor. Once it is, the loop is short — edit the flow, call it again, no restart or reinstall in between.
What it is
A Node package that exposes your Wordware apps to a local MCP client. You give it your Wordware API key; it discovers the flows you have deployed and makes them callable, so AI flows you built in Wordware become tools in your editor or desktop client.
What you get
- Automatic tool discovery — no app IDs to enumerate; what you have deployed is what appears
- An interactive setup that prompts for the key and can write the Claude configuration for you
- A local endpoint your own code can call as well, so the same flows are reachable over HTTP during development
- Configuration by .env file or by command-line flags, whichever suits how you launch it
- Usable straight from npx, installed globally as a command, or imported into a script
Requirements
A Wordware account, an API key created from the profile menu, and at least one app deployed — an undeployed flow will not appear. Run npx wordware-mcp to configure and start, or install globally and pass the key with a flag. WORDWARE_API_KEY and PORT are the two settings; the port defaults to 3000. Node is required. MIT licensed.
Setup effort
One command plus a key — npx wordware-mcp, then supply credentials
USE CASES
01
Calling a Wordware flow from your editor
Whatever you have deployed shows up as a tool, so a prompt chain you built visually is usable in a coding session.
02
Iterating on a flow while you use it
Change the app in Wordware and call it again — the next call picks up the change without a restart.
03
Hitting the same flows from your own code
Point an HTTP request at the local server during development instead of writing a second integration.
BEFORE YOU INSTALL
What to know first
Requires
- npx on PATH
- WORDWARE_API_KEY in your environment
INSTALLATION
Connect your client
This project publishes no client configuration, so the entry for your client is yours to write.
Server setup
TERMINAL
npx wordware-mcpnpx wordware-mcp asks for your Wordware API key and can write the Claude Desktop configuration for you. To skip the prompt, pass the key with --api-key, or put WORDWARE_API_KEY in a .env file in the folder you run it from.
