# Workato Developer API MCP

Your MCP server acts as a standard API platform user and supports Developer API token authentication. This lets you securely integrate with development environments using the same governance and access controls as the API platform. MCP tools built with API endpoints also allow you to pass authorization headers in API calls.

Workato Developer API MCP servers enable AI-powered developer environments like Claude Desktop and Cursor to programmatically access your Workato workspace for project and asset management.

FEATURE AVAILABILITY

MCP is available to all users in the US and EU data centers. MCP models are hosted in the US and EU data centers and respect data residency requirements. Contact your Customer Success representative if you're interested in using MCP.

# Install Developer API MCP for remote servers

You can install a remote MCP with a URL that authenticates with a token or through Workato Identity after you create an MCP server. The configurations in this section use Cursor and Claude Desktop.

NEED AN EXAMPLE?

Review the LLM, GitHub, and Workato Developer API use case for steps to create an MCP server integration that lets you create GitHub issues with natural-language commands in ChatGPT, Claude, or Cursor.

Complete the following steps to install the MCP remote server with a URL:

1

Sign in to Workato.

2

Configure your MCP integration:

# Pass authorization headers in API calls

You can call APIs with authorization headers within Workato recipe actions. You must use the header X-Wkt-Ext-Authorization datapill in your Workato recipe for APIM-collection-based MCP servers.

Complete the following steps to pass authorization headers in your API calls:

1

Go to project and click Create > Recipe.

Create a new recipeCreate a new recipe

2

Enter a name for your recipe in the Name field.

3

Use the Location drop-down menu to select the project where you plan to store the recipe.

4

Click Start building.

Start building your recipeStart building your recipe

5

Click Pick a starting point and select Trigger from an app.

6

Click Select an app and trigger event.

7

Search for and select API platform by Workato.

8

Select the New API request trigger. The New API request trigger in this use case doesn't require you to establish a connection.

New API request triggerNew API request trigger

9

Complete the following steps to configure your request schema:

1

Go to the Request headers section and click Add header.

2

Enter the following name in the Name field:

X-Wkt-Ext-Authorization
3

Optional. Provide a descriptive label for your header in the Label field.

4

Click Add field. Your header value is now accessible as a datapill under the New API request step output.

5

Map the X-Wkt-Ext-Authorization Step 1 datapill to the field where you plan to pass the header authorization.

Map your header authorization datapillMap the X-Wkt-Ext-Authorization datapill

6

Save your changes.

10

Go to AI Hub > MCP servers and select the MCP server that uses the recipe you created in the preceding steps.

11

Go to Settings > End user access and verify that Access Method is set to Token-based access.

12

Copy the Developer MCP Token URL that includes the wkt_token.

Copy the Developer MCP Token URLCopy the Developer MCP Token URL

13

Return to the Request schema section and click + Add Field.

14

Enter description in the Name and Label fields.

15

Use the Data type drop-down menu to select String.

16

Use the Optional drop-down menu to select No.

17

Use the Nest under drop-down menu to select payload.

18

Click Save.

19

Return to the Request schema section and click + Add Field.

20

Enter title in the Name and Label fields.

21

Use the Data type drop-down menu to select String.

22

Use the Optional drop-down menu to select No.

23

Use the Nest under drop-down menu to select payload.

24

Click Save.

Request schemaRequest schema

# Limitations

Workato Developer API MCP servers have the following limitations:

# Unsupported endpoints

The following Developer API endpoints aren't supported:


Last updated: 12/18/2025, 8:41:15 PM