Skip to main content
Glama
gmunro-lyft

Workato Dev MCP

by gmunro-lyft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Workato Dev MCP

No user-submitted related servers found.

    Related Servers

    • workday-studio-mcp

      andrew-price-huron
      F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that gives Claude direct access to Workday Studio workspace. Enables reading, writing, planning, and validating integration assemblies without network calls or tenant credentials.
      -

    • claudecode-mcp

      trevoraspencer
      A
      license
      A
      quality
      C
      maintenance
      Local MCP server that wraps the headless Claude Code CLI as MCP tools, providing stateless access to Claude's coding capabilities through prompt-based interactions. It enables users to execute Claude Code commands with various prompt formats and structured outputs directly from MCP clients.
      3
      MIT

    • MCP NodeServer

      Bing-Xuan-Lu
      A
      license
      Not graded
      quality
      B
      maintenance
      A Node.js MCP server that gives Claude Code direct access to file operations, database queries, PHP execution, SFTP deployment, and over 60 specialized tools for development and debugging.
      1
      MIT

    • mcp-workato

      chzkyy
      F
      license
      B
      quality
      C
      maintenance
      MCP server that exposes the Workato Platform API to Claude Desktop and other MCP clients, enabling management of recipes, jobs, connections, folders, custom connectors, and account properties through natural language.
      19
      -

    • salesforce-mcp

      ryu-727
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides comprehensive access to Salesforce Tooling API for metadata management, SOQL queries, code analysis, and debugging through Claude and other AI assistants.
      60 npm
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 56 tools

    Disambiguation4/5

    Most tools target distinct resource+action pairs, and descriptions clearly separate similar pairs like list_mcp_servers vs list_api_collections or query_lookup_table vs query_data_table. A few pairs (list_mcp_server_tools vs list_api_endpoints) could be confused at a glance, but the descriptions resolve the ambiguity.

    Naming Consistency4/5

    The overwhelming majority follow a consistent verb_noun underscore pattern (get_, create_, list_, update_, delete_, etc.). Minor exceptions like 'whoami' and 'workato_recipe_tips' break the pattern but are still readable and memorable.

    Tool Count1/5

    With 56 tools, this far exceeds the 50+ threshold defined as an extreme mismatch. Even for a broad platform covering recipes, MCP servers, API Platform, data tables, and RLCM, the sheer number creates a heavy cognitive load and suggests the server is over-scoped.

    Completeness4/5

    The tool set provides excellent lifecycle coverage across multiple domains: full CRUD for recipes and MCP servers, data table record operations, API endpoint activation, export/import, linting, and scaffolding. Minor gaps exist (no API endpoint create/delete, no collection update/delete) but core workflows have no dead ends.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources