Skip to main content
Glama

Related Servers

Alternatives to Operaton MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to discover and invoke operations from any OpenAPI service by managing deployments, authentication, and request building.
      48 PyPI
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to manage OSOP workflows by providing tools for validation, execution, testing, and optimization. It also supports converting workflows between OSOP and external formats like GitHub Actions, BPMN, and Airflow DAGs.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to access and execute automated decision services from IBM Decision Intelligence or IBM Automation Decision Services. It exposes deployed decision operations as tools for platforms like Claude Desktop and IBM watsonx Orchestrate.
      7
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables AI assistants to interact with Camunda Platform workflow engine. Provides 21 specialized tools for complete workflow automation and process management.
      21
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to integrate with IBM Business Automation Workflow by exposing workflow REST services as MCP tools, allowing natural language interaction with business automation capabilities.
      11
      Apache 2.0

    TDQS

    B3/5.0

    Scored across 105 tools

    Disambiguation3/5

    Most tools target distinct resource/action pairs, and ID-vs-key variants are generally explained. However, deployment_create, processDefinition_deploy, and decision_deploy overlap on artifact deployment, while task_setAssignee overlaps with task_claim and task_update; at 105 tools, misselection is likely.

    Naming Consistency4/5

    Names mostly follow a predictable resource_action pattern such as task_complete, processInstance_get, and migration_executeBatch. There are minor deviations in casing and operation grouping (e.g. getById/getByKey camelCase actions, deployment_create vs processDefinition_deploy), but the convention remains readable.

    Tool Count1/5

    105 tools is far beyond a well-scoped MCP surface and is extreme for this domain. Many ID/key variants, migration batch lifecycle operations, and separate list/count/get tools could have been consolidated.

    Completeness4/5

    The surface covers core BPM lifecycle operations widely: definitions, instances, tasks, jobs, incidents, deployments, history, users, groups, decisions, and migration. Some notable gaps remain, such as external tasks, message/signal correlation, tenant/authorization management, and form handling, but agents can work around most core workflows.

    Maintenance

    ActivityActive
    ResponsivenessLimited data