ci-watch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| watch_ciA | Чекає, поки GitHub Actions CI завершиться для поточного (або заданого) коміту в локальному git-репозиторії, і повертає підсумок ОДНИМ викликом: ok/conclusion/url, а за провалу - одразу хвіст логу невдалих кроків (--log-failed), без окремого запиту. Заміняє ручний цикл "push -> sleep -> gh run list -> (якщо впало) gh run view --log-failed". |
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 1 tool
Only one tool exists, so there is zero ambiguity in tool selection. The tool's purpose is clearly defined and distinct.
With a single tool, naming consistency is trivially maintained. The name 'watch_ci' is descriptive and follows a verb_noun pattern, though no comparison set exists to evaluate full consistency.
A single-purpose server with one tool is well-scoped. The tool encapsulates a complete workflow (waiting for CI and returning results), avoiding unnecessary fragmentation.
The tool covers the core CI-watching workflow effectively, including failure log retrieval. Minor gaps exist (e.g., no explicit cancel or list operations), but they are outside the tool's stated purpose and do not hinder its primary function.