workato

The Workato MCP Server exposes a set of tools that let you manage Workato recipes, connections, and metadata through the Model Context Protocol (MCP). Once the server is running, you can invoke tools such as list-recipes, create-recipe, start-recipe, and stop-recipe to manage lifecycle and execution of Workato recipes. Additional capabilities include listing and creating connections, discovering connectors, organizing assets into folders and projects, and monitoring activity logs and tags. This enables integration workflows with Cursor or Claude by providing a consistent MCP interface to Workato's API. The server also supports environment-specific configurations (dev, sandbox, prod) and structured filtering when querying resources, making it easier to manage large Workato workspaces programmatically.

Prerequisites:

• Node.js (v14+ recommended) and npm/yarn installed
• Access token for Workato API (required for authenticated operations)

Installation steps:

1. Clone the repository:

git clone <repository-url>
cd <repository-directory>

2. Install dependencies:

npm install
# or
yarn install

3. Build the server (if the project uses a build step):

npm run build

4. Run the MCP server locally (example):

npx your-package-name

Alternatively, use the generated dist/server.js with Node:

node dist/server.js

5. Configure Cursor or Claude to point at the MCP server as described in the configuration examples below.

Configuration tips:

• Use a descriptive server name in your MCP configuration (e.g., Workato MCP Server).
• Store sensitive tokens as environment variables and avoid hard-coding them in config files.
• For Cursor: add an MCP server with command: node and args: ["/path/to/your/project/dist/server.js"], and env: { "WORKATO_API_TOKEN": "<token>" }.
• For Claude Desktop: add an entry under mcp_servers with the same command/args and env settings.
• If you deploy in production, consider rotating the Workato API token and updating the MCP environment variables accordingly.
• Common issues often relate to path correctness for dist/server.js or missing environment variables; verify both when troubleshooting.
• The server exposes a rich set of tools as described in the README; consult the available tool list to determine supported actions for recipes, connections, connectors, folders, projects, and tags.