A comprehensive MCP server for Semaphore UI integration
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"semaphore-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Semaphore MCP Server  A Model Context Protocol (MCP) server for [Semaphore UI](https://semaphoreui.com/) - the modern open-source alternative to Ansible Tower/AWX. This server enables AI assistants and MCP-compatible tools to interact with Semaphore UI for managing Ansible, Terraform, and other automation workflows. ## Features - **Project Management** — List, create, and delete projects - **Task Management** — Launch, monitor, stop, and retrieve output of tasks - **Template Management** — CRUD operations on job templates - **Inventory Management** — Manage Ansible inventories - **Repository Management** — Manage Git repositories - **Environment Management** — Manage environment variable sets - **Key Store** — List and manage SSH keys and credentials - **Schedule Management** — Create and manage cron-based schedules - **User & Events** — Get user info and project event logs - **Server Info** — Check server health and version ## Installation ```bash pip install -e . ``` Or with the semaphore client from a local path: ```bash pip install -e /path/to/python3-semaphore-client pip install -e . ``` ## Configuration Copy `.env.example` to `.env` and configure: ```bash cp .env.example .env ``` Required environment variables: | Variable | Description | |----------|-------------| | `SEMAPHORE_URL` | Base URL of your Semaphore UI instance (e.g., `http://localhost:3000`) | | `SEMAPHORE_TOKEN` | API Bearer token (create via Semaphore UI or API) | Optional environment variables: | Variable | Default | Description | |----------|---------|-------------| | `READ_ONLY` | `true` | Set to `false` to enable write operations | | `DEBUG` | _(unset)_ | Set to `true` for verbose logging | ### Creating an API Token 1. **Via Web UI** (Semaphore 2.14+): Go to your user settings and create a token 2. **Via API**: ```bash # Login curl -c /tmp/semaphore-cookie -XPOST \ -H 'Content-Type: application/json' …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.