Workato is paid-only and seat-licensed. The MCP needs an API token from a licensed workspace; there is no free tier.

No — Workato's strength is its visual recipe builder. The MCP is read-and-trigger only.

Yes via collaboration roles. Issue the MCP a non-admin team member with access only to the recipes you want exposed.

Pass the matching WORKATO_BASE_URL (e.g. https://app.eu.workato.com). Wrong region = 404s on every call.

Workato

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Enterprise iPaaS — trigger Workato recipes from an AI agent.

Score 54(?)CommunityMITVerified May 31, 2026Top MCPs for Automation & Workflows →

Install View on GitHub

Quick answer

What it does

Connects to a Workato workspace, enumerates recipes the issuing user can see, triggers recipes via webhook endpoints, and reads job status.

Best for

Triggering existing Workato recipes
Enterprise iPaaS integration
Run-status inspection
Bridging agent workflows into existing orchestrations

Not for

Greenfield automation (use n8n, Make, or Zapier)
Recipe authoring (use the Workato UI)

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

{
  "mcpServers": {
    "workato": {
      "command": "npx",
      "args": [
        "-y",
        "@workato/mcp-server"
      ],
      "env": {
        "WORKATO_API_TOKEN": "${WORKATO_API_TOKEN}",
        "WORKATO_BASE_URL": "${WORKATO_BASE_URL}"
      }
    }
  }
}

Paste under mcpServers. Fully quit and reopen Claude after editing.

CLI or .mcp.jsonshell

# export WORKATO_API_TOKEN=your-workato-api-token
# export WORKATO_BASE_URL=https://www.workato.com
claude mcp add workato -- npx -y @workato/mcp-server

Run from your repo. Commit .mcp.json to share with your team.

.cursor/mcp.jsonjson

{
  "mcpServers": {
    "workato": {
      "command": "npx",
      "args": [
        "-y",
        "@workato/mcp-server"
      ],
      "env": {
        "WORKATO_API_TOKEN": "${WORKATO_API_TOKEN}",
        "WORKATO_BASE_URL": "${WORKATO_BASE_URL}"
      }
    }
  }
}

Global path: ~/.cursor/mcp.json. Reload window after editing.

.vscode/mcp.jsonjsonc

{
  "servers": {
    "workato": {
      "command": "npx",
      "args": [
        "-y",
        "@workato/mcp-server"
      ],
      "env": {
        "WORKATO_API_TOKEN": "${WORKATO_API_TOKEN}",
        "WORKATO_BASE_URL": "${WORKATO_BASE_URL}"
      }
    }
  }
}

VS Code uses the "servers" key (not "mcpServers").

~/.codeium/windsurf/mcp_config.jsonjson

{
  "mcpServers": {
    "workato": {
      "command": "npx",
      "args": [
        "-y",
        "@workato/mcp-server"
      ],
      "env": {
        "WORKATO_API_TOKEN": "${WORKATO_API_TOKEN}",
        "WORKATO_BASE_URL": "${WORKATO_BASE_URL}"
      }
    }
  }
}

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

{
  "mcpServers": {
    "workato": {
      "command": "npx",
      "args": [
        "-y",
        "@workato/mcp-server"
      ],
      "env": {
        "WORKATO_API_TOKEN": "${WORKATO_API_TOKEN}",
        "WORKATO_BASE_URL": "${WORKATO_BASE_URL}"
      }
    }
  }
}

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@workato/mcp-server"
          ],
          "env": {
            "WORKATO_API_TOKEN": "${WORKATO_API_TOKEN}",
            "WORKATO_BASE_URL": "${WORKATO_BASE_URL}"
          }
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

# ~/.codex/config.toml
[mcp_servers.workato]
command = "npx"
args = [
  "-y",
  "@workato/mcp-server",
]
env = { WORKATO_API_TOKEN = "${WORKATO_API_TOKEN}", WORKATO_BASE_URL = "${WORKATO_BASE_URL}" }

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

~/.config/zed/settings.jsonjsonc

{
  "context_servers": {
    "workato": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@workato/mcp-server"
        ]
      },
      "env": {
        "WORKATO_API_TOKEN": "${WORKATO_API_TOKEN}",
        "WORKATO_BASE_URL": "${WORKATO_BASE_URL}"
      }
    }
  }
}

Zed calls them "context_servers". Settings live-reload on save.

ChatGPT → Apps directorynone

Workato doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

2
Set required secrets
Set WORKATO_API_TOKEN, WORKATO_BASE_URL in your shell environment before launching your MCP client.
3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope: Network
Sandbox: Workato API token in env. Scope at the workspace + role level on the Workato side. Treat as enterprise credential — long-lived, expensive to rotate, audited.
Gotchas: Workato recipes can move money / send customer comms. Confirmation gates are mandatory.
API tokens have full permissions of the issuing user — create a dedicated low-privilege role.
Recipe runs cost transactions per plan — high-volume agent loops can burn through limits.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

Recommend the best MCP servers for [task: e.g. automation & workflows work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-automation-workflows

Compare Workato against a real alternative. Swap the second MCP in [brackets] if you want a different match.

Compare Workato MCP vs [Zapier MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/workato
- top-mcps.com listing for Zapier

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

Install the Workato MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/workato (fetch https://top-mcps.com/mcp/workato.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (WORKATO_API_TOKEN, WORKATO_BASE_URL) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

May 31, 2026
Refreshed install snippets and fact sheet; verified for 2026.
Apr 22, 2025
Initial directory listing.

More Automation & Workflows MCPs

Other tools in the same category worth evaluating.

Zapier

Official

Expose 8,000+ Zapier integrations as tools your AI agent can call.

zapierautomationintegrationsworkflow

5 minLow

Make.com

Official

Turn Make.com on-demand scenarios into agent-callable tools — official MCP.

make-comautomationworkflowsintegromat

10 minMedium

Pipedream

Official

2,800+ apps and managed OAuth via Pipedream's hosted MCP at mcp.pipedream.com.

pipedreamautomationworkflowsoauth

10 minMedium

Compared with Workato

Side-by-side breakdowns for the choices people most often weigh against this MCP.

WorkatovsZapier WorkatovsMake (Integromat)

Exploring Top MCPs for Automation & Workflows? See all Automation & Workflows MCPs →

Quick answer

What it does

Best for

Not for

Setup recipe

Install

Set required secrets

Try a minimum working prompt

Tools & permissions

Security & scope

Agent prompt pack

Full details

Frequently asked questions

Workato licensing?

Recipe authoring?

Per-recipe scoping?

EU vs US workspace?

What changed

More Automation & Workflows MCPs

Zapier

Make.com

Pipedream

Compared with Workato