# Workato

> Enterprise iPaaS — trigger Workato recipes from an AI agent.

[Canonical HTML page](https://top-mcps.com/mcp/workato) · [server.json](https://top-mcps.com/mcp/workato.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

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

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

### Claude Code — `CLI or .mcp.json`

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

```shell
# 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
```

### Cursor — `.cursor/mcp.json`

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

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

### VS Code — `.vscode/mcp.json`

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

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

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

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

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

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

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "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}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

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

```shell
# ~/.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}" }
```

### Zed — `~/.config/zed/settings.json`

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

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

### ChatGPT — `ChatGPT → Apps directory`

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.

```none

```

## At a glance

- **Maintainer:** Community
- **Transport:** stdio
- **Auth model:** API key
- **Required secrets:** WORKATO_API_TOKEN, WORKATO_BASE_URL
- **Supported clients:** Claude, Cursor, VS Code, Any MCP-compatible client, Workato workspace
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-05-31
- **Score:** 54/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/community-mcp/workato-mcp

## 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.

## 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)

## Description

A community-maintained MCP for Workato, the enterprise iPaaS. Trigger recipes via webhook endpoints, list recipes available to the issuing user, and inspect run status. Best fit for organisations that already use Workato as their integration platform and want an agent to be able to fire orchestrations the platform already owns.

## Why it matters

Workato is the integration platform many enterprises standardised on before LLM-driven workflows existed. An MCP turns existing recipes into agent-callable tools without re-implementation.

## Key features

- Workato API-token auth
- Recipe enumeration
- Webhook-based trigger
- Job-status inspection
- Workspace scoping

## FAQ

### Workato licensing?

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

### Recipe authoring?

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

### Per-recipe scoping?

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

### EU vs US workspace?

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

## Changelog

- **2026-05-31** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-04-22** — Initial directory listing.