Workflow86 Server

This is a fairly standard Node MCP Server implementation against the workflow86.com public API.

Standard Setup

Normal users will only need to follow some fairly standard setup steps:

1. Create an API Key from the Organization page of workflow86.com

2. Setup your MCP client

   • If you are using Cursor your config file will be at ~/.cursor/mcp.json
   • Claude on MacOS has a config file at ~/Library/Application\ Support/Claude/claude_desktop_config.json
   • For other tools please follow their setup instructions
   • Most tools use configuration in the following format:

   {
       "mcpServers": {
         "workflow86": {
             "command": "npx",
             "args": ["@npm-workflow86/mcp-server"],
             "env": {
                 "W86_API_KEY": "<API Key for your W86 Organization>"
             }
         }
       }
   }
   

   To use the latest unreleased build specify the canary tag eg.

             "args": ["@npm-workflow86/mcp-server@canary"],
   

3. Check your Node Version
   Make sure your system default node version is v22 or greater (20 may also work but your mileage may vary)

   node -v
   

Note: The server will start even if W86_API_KEY is not set so MCP clients can discover available tools. However, calling any Workflow86 tool requires an API key (or custom W86_HEADERS). Without it, tool calls will fail with an authorization error.

Optional: set W86_DOMAIN to point at a different API host (defaults to https://api.workflow86.com).

Test Integration

Cursor

Goto Cursor -> Settings -> Cursor Settings -> Tools & Integrations

There should be a workflow86 entry in the MCP Tools section. If something's gone wrong an error message will display here.

Contributor Setup

For other folk that would like to run the server against source for whatever reason setup is a little more involved. If you don't already have the source run:

 git clone [email protected]:workflow86oss/mcp-server.git

Build

npm install && npm run build

Tests and Coverage

• Run unit tests: npm test
• Run module tests: npm run moduleTest
• Analyze coverage for module tests: npm run moduleCoverage
  • Uses c8 (V8 coverage) so child processes spawned by module tests are included
  • First run npm install to ensure dev deps (c8) are installed
  • HTML and lcov reports: coverage/module/ (open coverage/module/index.html)

Run with CLI

This is particularly useful to get at logs easily if things are going wrong or for quick testing:

First setup your Dev API Key (you might like to add this to your shell init script)

  export W86_API_KEY=<api key>

Then you can invoke commands via jsonrpc like this:

  echo '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list-workflows","arguments":{}}}' | node build/server.js

Configure a MCP Client

To configure a MCP Client to run against your local checkout put this config in the correct place for your desired tool:

{
    "mcpServers": {
      "workflow86": {
          "command": "node",
          "args": ["/<absolute-checkout-path>/mcp-server/build/server.js"],
          "env": {
              "W86_API_KEY": "<API Key for your W86 Client>"
          }
      }
    }
}

Regenerate Generated Client Code

src/client contains a typescript client generated from the Public API OpenAPI spec at https://api.workflow86.com/v3/api-docs. To regenerate after API changes:

npm run genclient

References

Workflow86 homepage: https://www.workflow86.com
MCP Spec: https://modelcontextprotocol.io/specification/2025-06-18