mcp-workato
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKATO_POD | No | Workato data center pod (e.g., us, eu, sg, jp, au, il, kr, cn, trial). | us |
| WORKATO_DEBUG | No | Log each API request to stderr. | false |
| WORKATO_TOKEN | No | API token for Workato. Used for API Token mode (default) or Access Token mode when combined with WORKATO_USER_ID. | |
| WORKATO_USER_ID | No | Numeric Workato user ID, required for Access Token (legacy) mode. | |
| WORKATO_BASE_URL | No | Override the API base URL completely. | |
| WORKATO_AUTH_MODE | No | Force authentication mode: 'api_token', 'access_token', or 'oauth2'. Defaults to auto-detection. | |
| WORKATO_CLIENT_ID | No | OAuth2 client ID, required for OAuth2 mode. | |
| WORKATO_TOKEN_URL | No | Override the OAuth2 token URL. | |
| WORKATO_TIMEOUT_MS | No | HTTP request timeout in milliseconds. | 60000 |
| WORKATO_CLIENT_SECRET | No | OAuth2 client secret, required for OAuth2 mode. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Validate Workato credentials and return the current user. Use this first to confirm the connection works. |
| list_recipesA | List recipes belonging to the authenticated user (GET /api/recipes). Supports filtering by folder, adapters (connectors), running status, and date range. Results are paginated (default: per_page=100, max 100). Set exclude_code=true to speed up listing for large accounts. Note: The Workato API does NOT support server-side name search. To find recipes by name, use the |
| search_recipesA | Search recipes by name (case-insensitive). Since the Workato API has no server-side text search, this tool auto-paginates through all recipes and filters client-side by name. Example: search_recipes({ name: 'PRDI Recipe 04 - PRDI AR DOKU Transactions' }) |
| get_recipeA | Get full details of a single recipe by id (GET /api/recipes/:id). Returns name, description, code (recipe DSL), config (connections), trigger, running status, job counts, tags, version info, etc. Pass includes=['tags'] to also retrieve the recipe's tag handles. |
| start_recipeC | Start (enable) a recipe (PUT /api/recipes/:id/start). |
| stop_recipeA | Stop (disable) a recipe (PUT /api/recipes/:id/stop). |
| force_run_recipeC | Force-run a recipe on demand (POST /api/recipes/:recipe_id/force_run). Rate limit: 1 request per second. |
| delete_recipeB | Delete a recipe permanently (DELETE /api/recipes/:id). |
| reset_recipe_triggerA | Reset a recipe trigger cursor (POST /api/recipes/:recipe_id/reset_trigger). Use to re-sync data from the source. Only works with polling and scheduled triggers. The recipe must handle duplicate records. |
| list_jobsC | List jobs, optionally filtered by recipe_id, status, or date range. Useful for monitoring recipe execution history. |
| get_jobA | Get details of a single job by id, including its input/output and error trace. |
| list_connectionsC | List connections configured in the account. |
| get_connectionA | Get details of a single connection by id. |
| list_foldersC | List project folders in the account. Folders group recipes and connections. |
| get_folderB | Get details of a folder/project by id. |
| list_custom_connectorsC | List custom connectors in the account. |
| get_custom_connectorA | Get metadata of a custom connector by id. |
| get_custom_connector_codeB | Get the source code (block DSL) of a custom connector by id. |
| list_account_propertiesA | List account properties (named constants) defined in the Workato account. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |