mcp-workato
Related Servers
Alternatives to mcp-workato
No user-submitted related servers found.
Related Servers
- FlicenseBqualityCmaintenanceA local, zero-dependency MCP server to author, lint, deploy, and debug Workato recipes from Claude. It wraps the Workato Developer REST API, RLCM package API, and Data Tables record API with 56 tools.56-
- FlicenseBqualityCmaintenanceA standalone MCP server that enables Claude Desktop to manage Clio legal practice matters, documents, billing, and more via ~46 tools, with secure OAuth and audit logging.46-
- AlicenseAqualityDmaintenanceMCP server that gives Claude Desktop and other desktop MCP clients filesystem powers—read, write, edit, and manage files like AI coding assistants.1752 npm9MIT
- AlicenseBqualityDmaintenanceA comprehensive MCP server for Dataiku DSS integration, providing Claude Code with direct access to manage recipes, datasets, and scenarios.4413 npm1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that lets Claude and any other MCP-compatible client work with an OpenText AppWorks Platform tenant in plain English.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that connects Claude Desktop to Atiendo24 platform, enabling management of appointments, customers, conversations, leads, analytics, and WhatsApp messaging through natural language.11 npmMIT
TDQS
Scored across 19 tools
Each tool targets a clear resource-action pairing: recipes have list/search/get/start/stop/force_run/delete/reset_trigger, while jobs, connections, folders, and custom connectors each have their own list/get tools. The only potentially overlapping tools, list_recipes and search_recipes, are explicitly differentiated by their descriptions.
Tool names follow a consistent verb_noun pattern: list_*, get_*, start_recipe, stop_recipe, force_run_recipe, delete_recipe, reset_recipe_trigger. The only non-verb_noun name is 'ping', which is a standard exception for connectivity checks.
With 19 tools, the set is slightly heavy but each tool serves a distinct purpose within the Workato domain (recipe lifecycle, jobs, connections, folders, custom connectors, account properties). The count is justified for the API surface covered, though it edges past the typical 'well-scoped' 3-15 range.
The tool set offers comprehensive read, list, and lifecycle operations for recipes (start, stop, force-run, delete, reset trigger) and read operations for other resources. However, recipe creation and update are missing, which are significant gaps for fully managing recipes via the server.