AIRO MCP server ​

The AIRO MCP server exposes Workato AIRO's full platform capabilities to MCP-compatible AI clients, including Claude Code, Claude Desktop, Cursor, ChatGPT, and Codex CLI. This enables you to build recipes, manage Genies, create MCP servers, and manage data table schema directly from your AI development environment using natural language.

AIRO as an MCP serverAIRO as an MCP server

How it works ​

The AIRO MCP server supports two authentication methods:

  • OAuth 2.0: Recommended for interactive clients. Your MCP client opens a browser window the first time you connect. The window displays Workato's authorization screen, which lists the permissions requested by the client. Click Authorize to complete the connection. Refer to Connect using OAuth 2.0 for the setup steps.
  • API token: Recommended for headless or configuration-driven setups. Pass a Workato API token as a bearer header. Refer to Connect using an API token for the setup steps.

The server exposes tools organized into the following categories:

CategoryWhat you can do
RecipesCreate, edit, search, and manage recipes, including step-level operations, field mapping, conditions, and connections
Skills and MCPConvert recipes to skills and create or manage MCP servers
Custom connectorsBuild, edit, and save custom connector SDK code
Genies and knowledge basesCreate and configure Genies, manage knowledge bases, and assign knowledge sources
Blueprints and assetsWork with blueprints, asset maps, and asset metadata
DataCreate and manage data table schema
Jobs and testsInspect job history and manage test cases

The tools available to you depend on your workspace features and the identity the connection uses:

  • OAuth 2.0: The server uses the permissions of the authenticated user.
  • API token: The server uses the workspace owner's identity and permissions. The AIRO MCP Server permission on the API client role gives the token access to the server and all the tools available in your workspace. Other privileges assigned to the role and the API client's project access settings don't limit the token's access to tools or projects in the workspace.

The activity audit log attributes actions that the AIRO MCP server takes to the authenticated user for OAuth 2.0 connections, or to the workspace owner for API token connections, with a (via AIRO) label.

Agents call the docs_get tool to get instructions, per-tool guides, and a live index of the tools available to them. Prompt your MCP client to call docs_get when you need information about a specific tool.

Prerequisites ​

You must have the following before you configure the AIRO MCP server:

  • A Workato account with AIRO access
  • An MCP-compatible client installed, such as Claude Code, Claude Desktop, Cursor, ChatGPT, or Codex CLI

Some MCP client configurations use npx. These configurations require Node.js to be installed and available in your PATH. Run node -v in your terminal to verify your installation.

API token authentication also requires a Workato API token. Refer to Generate an API token for instructions.

Data center server URLs ​

The AIRO MCP server URL depends on the data center where your Workato workspace is hosted. Developer Sandbox workspaces always use the trial URL. Use the server URL that matches your workspace region:

Data centerAIRO MCP server URL
UShttps://app.workato.com/airo_mcp
EUhttps://app.eu.workato.com/airo_mcp
JPhttps://app.jp.workato.com/airo_mcp
SGhttps://app.sg.workato.com/airo_mcp
AUhttps://app.au.workato.com/airo_mcp
ILhttps://app.il.workato.com/airo_mcp
KRhttps://app.kr.workato.com/airo_mcp
UKhttps://app.uk.workato.com/airo_mcp
Developer Sandboxhttps://app.trial.workato.com/airo_mcp

The AIRO MCP server isn't available in the CN data center. Refer to feature availability in the China data center for more information.

VIRTUAL PRIVATE WORKATO (VPW) CUSTOMERS

This page provides general guidance for all Workato users. If you're a Virtual Private Workato (VPW) customer, refer to your private documentation for detailed configuration guidance specific to your instances.

Connect using OAuth 2.0 ​

Complete the following steps to connect the AIRO MCP server to your MCP client using OAuth 2.0:

WORKSPACE AND ENVIRONMENT SCOPE

OAuth 2.0 scopes each AIRO MCP server connection to the Workato workspace and environment active in your browser session. Sign in to the target workspace and environment before you start authorization. Repeat the authorization steps for a different workspace or environment, or create a separate connection for each workspace and environment you need to access at the same time.

Connect using an API token ​

API token authentication requires a Workato API token.

API TOKENS HAVE FULL WORKSPACE ACCESS

Connections that authenticate with an API token perform actions with the workspace owner's identity and permissions. The AIRO MCP Server permission on the client role gives access to the server and all the tools available in your workspace. The role's other privileges and the API client's project access settings don't apply, so the MCP client can access every project in the workspace. Connect using OAuth 2.0 to limit what an MCP client can access.

Generate an API token ​

Complete the following steps to obtain an API token:

1

Sign in to Workato.

2

Go to Workspace admin > API clients > Client roles.

3

Open an existing client role or create a client role.

4

Go to the Tools tab.

5

Select the AIRO MCP Server checkbox in the AIRO MCP tools section.

The AIRO MCP Server checkbox selected in the AIRO MCP tools section of a client roleSelect AIRO MCP Server on the Tools tab of the client role

6

Click Save changes.

7

Assign this client role to an existing API client, or select the role when you create a new API client.

8

Copy and securely store the API client token.

Configure your MCP client ​

Complete the steps for your MCP client:

Connect to multiple workspaces or environments ​

You can connect to multiple Workato workspaces or environments by adding a separate server entry to your MCP configuration for each connection. Use a unique server name and API token for every entry.

Each API client is assigned to one environment in workspaces with environments enabled. Its API token works only with that environment.

For example, the following Claude Desktop configuration uses the URL for your data center to connect to the Development and Production environments in the same workspace:

json
{
  "mcpServers": {
    "workato-airo-mcp-server-dev": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://YOUR_DATA_CENTER/airo_mcp",
        "--transport",
        "http-first",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <DEV_API_TOKEN>"
      }
    },
    "workato-airo-mcp-server-prod": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://YOUR_DATA_CENTER/airo_mcp",
        "--transport",
        "http-first",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <PROD_API_TOKEN>"
      }
    }
  }
}

For example, on the US data center, the URL is https://app.workato.com/airo_mcp for both server entries above.

The other MCP clients use the same approach: repeat the setup steps with a distinct server name and token for each connection.

Use cases ​

The following examples demonstrate common workflows with the AIRO MCP server.

Build and test a recipe ​

Use AIRO to create a multi-step recipe from a natural language description, then save and test it without leaving your development environment.

Create a recipe that syncs new Salesforce opportunities to Jira issues.
Add an OpenAI step to summarize the opportunity before creating the Jira issue.
Save the recipe and show me the test cases.

Create a genie with knowledge sources ​

Set up a genie and connect it to relevant knowledge bases so it can answer domain-specific questions.

Create a new genie called "Sales Intelligence" and assign the CRM knowledge base to it.

Build an MCP server ​

Create an MCP server from your workspace assets so other AI clients can connect to your tools.

Build an MCP server called "Sales Tools" using the lead enrichment and deal scoring skills from the Sales Automation project.

Investigate job failures ​

Inspect recent job history to diagnose errors in production recipes. The agent calls job_list to find a failed job, then job_get to analyze the job's status and suggest a fix for the recipe.

List the last 10 jobs for recipe 1555928 and show me any errors.

Manage a data table ​

Create a data table and define its schema without leaving your development environment.

Create a data table to store approver thresholds by region.

Build a custom connector ​

Build a connector for an API that isn't available as a platform connector, using your own development environment instead of the Workato SDK editor.

Build a connector for the National Weather Service API at https://www.weather.gov/documentation/services-web-api.
Add an action that retrieves active weather alerts for a state or territory.

Refer to Build custom connectors with AIRO MCP for the full workflow, including how saving and releasing changes work.

Last updated: