swarm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SWARM_BIN | No | Path to the swarm binary (default: 'swarm' on PATH) | swarm |
| SWARM_WORKSPACE | Yes | The workspace root path for swarm-mcp |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| swarm_get_statusA | The derived workspace board — specs, their tasks, and review status. Read-only; no verdict. |
| swarm_check_workspaceA | Run the Swarm checks contract over every spec + change plan. Returns diagnostics, never a verdict. |
| swarm_check_fileA | Run the Swarm checks contract over one file (spec / task / review / change-plan). Returns diagnostics, never a verdict. |
| swarm_scan_taskA | Reconcile a task against its spec and the worktree diff to surface coverage gaps, out-of-scope changes, and self-report mismatches — before a review packet exists. Same engine as reconcile_review. Never a verdict. If the task has no live worktree, returns a structured "not runnable here" result, not an error. |
| swarm_reconcile_reviewA | Reconcile a finished run: compare task, spec, review packet, and git diff. Returns coverage gaps, empty-evidence Pass rows, scope drift, and self-report mismatches as facts + a derived human-attention list. Never issues a final verdict — a human or an independent reviewer owns the result. |
| swarm_validate_review_packetA | Run the review-file checks (C012 coverage, C013 verify-evidence) over a review packet: structure, status, and that Pass rows carry evidence. The diff-aware half (out-of-scope, self-report) comes from reconcile_review when a worktree exists. Returns diagnostics, never a verdict. |
| swarm_get_taskA | The task packet`s scope, affected areas, claimed changes, and frontmatter (id/source/status). Read-only. |
| swarm_get_specA | The spec`s frontmatter, requirements (id + line + named verify command), and sections. Read-only. |
| swarm_get_reviewA | The review packet |
| swarm_get_checksA | The checks contract — version + the core checks (id/name/severity). What review must satisfy. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| swarm_task_briefing | Prepare to work on a task: read its scope, do-not-change list, verify items, and open questions first. |
| swarm_before_done | The implementer-facing pre-handoff check: clean the mechanical drift you can see — but you cannot sign off. |
| swarm_review_assistant | Help an INDEPENDENT reviewer: re-derive the facts, treat a clean reconcile as something to falsify, not trust. |
| swarm_evidence_rule | A claim is not evidence; an empty Evidence cell is Unverified, never Pass. |
| swarm_finding_candidate | Scaffold a durable finding from a discovered fact — as a candidate, never accepted. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| workspace | Workspace root, mode, and the current board summary. |
| status | The derived workspace board — specs, tasks, reviews, gaps. |
| checks | The checks contract — version + the core checks. |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: checking files vs workspace, getting different entities (checks, review, spec, status, task), reconciling reviews, scanning tasks, and validating packets. No overlapping functionality.
All tools follow the consistent pattern 'swarm_verb_noun' using snake_case. Verbs are appropriate (check, get, reconcile, scan, validate) and nouns are specific, making the set predictable and easy to navigate.
10 tools is well-scoped for a server focused on analysis and verification of specifications, tasks, and reviews. Each tool serves a necessary function without redundancy or bloat.
The tool surface covers all essential operations for the server's analysis purpose: checking, retrieving all relevant entities, reconciling, scanning, and validating. No obvious gaps given the read-only/analysis scope.