Skip to main content
Glama
cloin

SemaphoreUI MCP Server

by cloin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to SemaphoreUI MCP Server

No user-submitted related servers found.

    Related Servers

    • semaphore-mcp-server

      VitexSoftware
      A
      license
      C
      quality
      B
      maintenance
      Enables AI assistants to interact with Semaphore UI for managing Ansible, Terraform, and other automation workflows through project, task, template, and inventory management.
      37
      MIT

    • rundeck-mcp-server

      mariomorenodev
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to manage Rundeck operations including jobs, executions, projects, nodes, system management, key storage, webhooks, and ACL policies via natural language.
      50
      35 npm
      1
      Apache 2.0

    • awx-mcp-server

      SurgeX-Labs
      F
      license
      Not graded
      quality
      D
      maintenance
      Industry-standard MCP server for AWX/AAP/Ansible Tower automation, enabling AI agents to manage job templates, launch and monitor jobs, and handle inventories and projects through natural language.
      11
      -

    • MCP Ansible Server

      bsahane
      F
      license
      Not graded
      quality
      F
      maintenance
      Enables comprehensive Ansible automation management through natural language, including playbook creation and execution, inventory management, role scaffolding, and project workflows. Supports both local inventories and full project lifecycle management with syntax validation and idempotency testing.
      30
      -
    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

    C2.8/5.0

    Scored across 69 tools

    Disambiguation2/5

    Several tools overlap heavily: get_last_events and list_events are effectively the same operation with the same limit argument, and list_tasks/filter_tasks both provide status/tag filtering. The failed-task analysis family (analyze_task_failure, bulk_analyze_failures, get_latest_failed_task) also blurs boundaries, so agents can easily select the wrong tool despite generally distinct resource families.

    Naming Consistency4/5

    Most tools follow a predictable lower_snake verb_noun pattern (list_, get_, create_, update_, delete_ per resource). Minor deviations such as get_last_events vs list_events, list_inventory as a plural list, and asymmetric failure-analysis names prevent a perfect score.

    Tool Count1/5

    69 tools is far into the extreme range for an MCP server and will flood the agent's context and tool-selection space. Even though SemaphoreUI has many resource types, nearly every CRUD and bulk variant is exposed; a curated 15-25 tool surface would be far more appropriate.

    Completeness3/5

    The server covers most major Semaphore resources with full CRUD lifecycles: projects, templates, vistas, schedules, tasks, environments, inventory, repositories, access keys, users, and backups. However, secret management (a core Semaphore concept referenced by vaults/backups) is absent, and there is no global user lookup to supply user_id when adding project users.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources