semaphore-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Set to true for verbose logging | |
| READ_ONLY | No | Set to false to enable write operations | true |
| SEMAPHORE_URL | Yes | Base URL of your Semaphore UI instance (e.g., http://localhost:3000) | |
| SEMAPHORE_TOKEN | Yes | API Bearer token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| project_listA | List all projects accessible to the current user. Returns: JSON list of projects with their details. |
| project_getB | Get details of a specific project. |
| project_createC | Create a new project. |
| project_deleteC | Delete a project. |
| task_listC | List all tasks in a project. |
| task_getC | Get details of a specific task. |
| task_launchC | Launch a new task from a template. |
| task_stopB | Stop a running task. |
| task_outputB | Get the output log of a task. |
| task_deleteB | Delete a task. |
| template_listB | List all templates in a project. |
| template_getB | Get details of a specific template. |
| template_createC | Create a new template (job template). |
| template_deleteD | Delete a template. |
| inventory_listB | List all inventories in a project. |
| inventory_getC | Get details of a specific inventory. |
| inventory_createB | Create a new inventory. |
| inventory_deleteC | Delete an inventory. |
| repository_listA | List all repositories in a project. |
| repository_getB | Get details of a specific repository. |
| repository_createC | Create a new repository. |
| repository_deleteC | Delete a repository. |
| environment_listA | List all environments in a project. |
| environment_getA | Get details of a specific environment. |
| environment_createC | Create a new environment. |
| environment_deleteC | Delete an environment. |
| key_listB | List all keys (credentials) in a project. |
| key_getB | Get details of a specific key. |
| key_deleteC | Delete a key. |
| schedule_listB | List all schedules in a project. |
| schedule_createB | Create a new schedule for a template. |
| schedule_deleteB | Delete a schedule. |
| user_get_currentA | Get the current authenticated user's information. Returns: JSON object with current user details. |
| user_tokensA | List API tokens for the current user. Returns: JSON list of API tokens. |
| event_listC | List events for a project. |
| server_infoA | Get Semaphore server information (version, configuration). Returns: JSON object with server info. |
| server_pingA | Ping the Semaphore server to check connectivity. Returns: Ping response confirming the server is reachable. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 37 tools
Each tool targets a specific resource and action (e.g., environment_create, inventory_list), with no overlapping descriptions. Even similar tools like server_info and server_ping have clearly distinct purposes.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., environment_create, task_get). No mixing of conventions or abbreviations.
With 37 tools, the count is well above the recommended range for coherence (16-25 feels heavy; 37 is excessive). While the domain is broad, many tools could be consolidated or are unnecessary for core workflows.
Missing update operations for environment, inventory, project, repository, schedule, and template. Also missing key_create. These gaps hinder full lifecycle management and may cause agent failures.