MCP usage ​

Workato measures MCP usage based on the underlying asset the MCP server invokes.

Some plans measure MCP usage in MCP calls rather than by the underlying asset's metric. Refer to your contract or contact your Customer Success Representative for more information.

How MCP usage is measured ​

Workato measures usage based on what the server invokes when an external agent or client calls a Workato MCP server. Refer to the metric page for the underlying asset to see how its usage is calculated.

MCP calculation rules ​

MCP usage calculations follow the general usage calculation rules. In addition:

• Workato attributes usage to the underlying asset, not the MCP server.
• Skills invoked over MCP are billed as Tasks.
• Recipe functions exposed directly as an MCP tool run as independent workflows and are measured in Tasks. Recipe functions called synchronously from another MCP-exposed asset (such as a workflow or API recipe) inherit the calling asset's usage metric. Refer to Tasks for more information.
• IDP (Pages) and Event streams (Events) are counted in addition to the invoked asset's usage metric when applicable.

MCP usage examples ​

The following examples demonstrate how Workato calculates MCP usage for common underlying assets. Refer to Skills, Managed API, API Proxy, or Tasks for the underlying calculation rules.

Skill invoked over MCP ​

Managed API invoked over MCP ​

API Proxy invoked over MCP ​

Recipe function invoked over MCP ​