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.
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.
- 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
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.
One command plus a key — npx wordware-mcp, then supply credentials