RELATED 01
CodeQL Development MCP Server
OFFICIAL SERVERWrite, test, run and profile CodeQL queries from an AI assistant through the local CodeQL CLI
39GitHub stars
838/wknpm downloads
51popularity score
Workato Developer API MCP Server
Hosted MCP endpoint for managing a Workato workspace through its Developer and Embedded APIs
Official · workato.com Remote (hosted) · Streamable HTTP Developer toolsCloud platforms
Connect your client
Remote (hosted)
Add in one click
Opens the app, which asks before it adds the server. Then replace each <NAME> in its settings with your value.
Or add it by command or config
Claude CodeTerminal
claude mcp add --transport http workato-developer-api https://app.workato.com/mcp --header 'Authorization: Bearer <API_TOKEN>'Cursor~/.cursor/mcp.json
{
"mcpServers": {
"workato-developer-api": {
"url": "https://app.workato.com/mcp",
"headers": {
"Authorization": "Bearer <API_TOKEN>"
}
}
}
}VS Code.vscode/mcp.json
{
"servers": {
"workato-developer-api": {
"type": "http",
"url": "https://app.workato.com/mcp",
"headers": {
"Authorization": "Bearer <API_TOKEN>"
}
}
}
}Codex~/.codex/config.toml
[mcp_servers.workato-developer-api]
url = "https://app.workato.com/mcp"
http_headers = { "Authorization" = "Bearer <API_TOKEN>" }Gemini CLITerminal
gemini mcp add --scope user --transport http --header 'Authorization: Bearer <API_TOKEN>' workato-developer-api https://app.workato.com/mcpWhat it does
Workato runs this server itself at https://app.workato.com/mcp. It turns the Workato Developer API, and the Embedded API for Embedded admin workspaces, into MCP tools, so an assistant in Claude Desktop, Cursor or another client can look at and change what lives in a workspace: recipes, connections, jobs, folders, projects and tags. Workato's examples include moving a folder under a new parent, listing the folders in a project, grouping connections by active and inactive status, listing the jobs of a recipe and creating tags.
There is no fixed tool list. The tools an assistant sees are the API endpoints switched on in the API client role behind the token, set under Workspace admin > API clients, and that role's project scopes apply too. One token can therefore expose a read-only set of tools for one project, while another can create, update and delete across the whole workspace.
The API client page adds details the MCP page leaves out: a client can be limited to allowed IP ranges, its token is shown only once and must be regenerated if lost (regenerating breaks the old token, and legacy tokens cannot be regenerated), and Developer API tokens are covered by GitHub secret scanning (api-clients documentation).
What it needs
A Workato workspace in the US, EU, AU, JP, SG, IL, KR or UK data center (not CN), and a Developer API client token whose client role enables the endpoints you want as tools; Embedded API use needs a token created in an Embedded admin workspace. Clients that cannot send headers to a remote server, such as Claude Desktop, use Node.js to run npx mcp-remote with an Authorization header, as Workato's docs show.
Limits
Workato lists endpoints the MCP server does not support: Developer API event streams and lookup tables, and Embedded API lookup tables. Tools are limited to the endpoints and projects allowed in the API client role. Not offered to workspaces in the CN data center. Cursor only sees tools present when a chat starts, so a new chat is needed after changing the configuration.
Who it suits
Suits Workato administrators and developers who want an assistant to audit or tidy a workspace: list recipes, jobs and connections, reorganise folders and projects, or create tags, without writing API scripts. As Workato's own hosted server, it needs nothing installed beyond a client, but every call runs on Workato's side against a live workspace, so a narrowly scoped API client is the sensible start. Pick something else for lookup tables or event streams, which it does not cover, or for a CN data center workspace.