Workato MCP Server

Workato MCP is a provider-hosted Model Context Protocol service that turns Workato assets (API recipe collections, skills, and AI gateway collections) into tools that any MCP-compatible LLM client can call. Builders create an MCP server inside the Workato AI Hub, pick which recipes or API endpoints to expose, and Workato issues a unique authenticated remote MCP URL that agents like Claude, ChatGPT, Cursor, or Workato Genies can attach to.

The platform is positioned as Workato's "Enterprise MCP" layer for connecting AI agents to enterprise systems such as Salesforce, Slack, Marketo, NetSuite, ServiceNow, and Workday, leveraging Workato's existing connector library. It adds Verified User Access (VUA) so agent actions inherit the authenticated user's identity, plus role-based access control, audit logs, rate limits, usage quotas, and IP allow/block lists. Servers can be assembled from project assets without code, or deployed from the prebuilt MCP server registry.

A separate Workato Developer API MCP server is also available at https://app.workato.com/mcp, which exposes the Workato platform itself (folders, projects, connections, recipes, jobs, tags, etc.) to agents using Developer or Embedded API tokens. MCP is hosted in US, EU, and APAC regions and respects data residency; it is not available in the CN data center.

Tools

Prerequisites

• A Workato account with access to the AI Hub
• Assets to expose (API recipe collection, skill, or AI gateway collection) inside a single Workato project
• For the Developer API MCP: a Developer API or Embedded API token created under Workspace admin > API clients

Create an MCP server in Workato

• Sign in to Workato and open AI Hub > MCP Servers
• Click + Create an MCP server (or use the Projects page > Create > MCP server)
• Enter a server name and optional description
• Choose the project containing the assets you want to expose
• Set Tool source to either Project assets or API collection
• Select the specific tools to expose and click Start building
• Open the server's Overview tab to copy the remote MCP URL and the Developer MCP Token

Connect from Claude Desktop

Workato is a remote MCP server, so use mcp-remote to bridge it into Claude Desktop:

{
  "mcpServers": {
    "workato": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://app.workato.com/mcp",
        "--header",
        "Authorization: Bearer <YOUR_WORKATO_MCP_TOKEN>"
      ]
    }
  }
}

Connect from Cursor

Cursor supports remote MCP servers natively:

{
  "mcpServers": {
    "workato": {
      "url": "https://app.workato.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_WORKATO_MCP_TOKEN>"
      }
    }
  }
}

Replace <YOUR_WORKATO_MCP_TOKEN> with the token from the server's Overview tab (or a Developer/Embedded API token if you are connecting to the Workato Developer API MCP). Restart the client after editing the config.

Governance options

In the server settings you can configure rate limits (e.g. 5,000 calls/hour), usage quotas (e.g. 1M calls/month), and IP allow/block lists. Logs are available under Tools > Logs filtered by MCP server.

• Expose a Salesforce recipe collection so agents can search leads, update opportunities, and log activities through natural-language prompts
• Let a ChatGPT or Claude agent operate the Workato platform itself: create projects, list jobs, manage connections, and run recipe health analyses via the Developer API MCP
• Wrap an internal HR or finance API (NetSuite, Workday, ServiceNow) in an API collection and expose only the endpoints approved for AI use, governed by rate limits and IP allow lists
• Build a customer support agent that calls a Zendesk Knowledge Base prebuilt MCP server plus a custom ticket-triage skill recipe in one server
• Give Cursor or Workato Genies access to AI gateway collections so prompts route through governed enterprise LLMs with audit trails and Verified User Access

• "Find all open Salesforce opportunities over $50k closing this quarter and post a summary to #sales-pipeline in Slack."
• "Using the Workato Developer API, list every recipe in the Marketing project that has failed in the last 24 hours and show the error message."
• "Create a new Workato folder called 'Q3 Launch' under the Marketing project and add the staging Salesforce connection to it."
• "Look up the Zendesk knowledge base article for SSO troubleshooting and draft a reply to ticket #48213."
• "Run a recipe health analysis on the NetSuite invoice sync and list any recipes flagged as unhealthy."

• Officially hosted and maintained by Workato with enterprise governance: role-based access, audit logs, rate limits, quotas, and IP restrictions
• Turns existing Workato recipes, skills, and API collections into MCP tools without writing MCP server code
• Verified User Access ties agent actions to the calling user's identity for compliant, auditable automation
• Prebuilt server registry accelerates rollout for common systems like Salesforce, Zendesk, ServiceNow, and GitHub

• Requires a paid Workato account and AI Hub access; not usable without an existing Workato workspace
• Not available in the CN data center, and custom domains are not supported (must use app.workato.com/mcp)
• Developer API MCP does not expose Event Streams or Lookup Tables endpoints
• Tool set is only as complete as the underlying recipes/API collections you build, so initial setup work is required

• Zapier MCP for exposing Zapier actions across thousands of apps to AI agents
• Make MCP scenarios via community MCP bridges for similar low-code automation coverage
• n8n self-hosted workflows with community MCP server implementations