swarm-mcp
The swarm-mcp server provides workspace inspection, reconciliation, and safe-write scaffolding for a spec/review discipline system. All outputs surface facts and diagnostics — never a pass/fail verdict (noVerdictIssued: true), keeping authority with human reviewers.
Workspace Status & Checks
swarm_get_status: Retrieve the derived board showing specs, tasks, and review statuses.swarm_check_workspace: Run the checks contract over every artifact in the workspace, returning diagnostics.swarm_check_file: Run checks against a single file (spec, task, review, or change-plan) by path.swarm_get_checks: Retrieve the checks contract (version, check IDs, names, severities).
Inspect Artifacts
swarm_get_task: Get a parsed task packet — scope, affected areas, claimed changes, frontmatter.swarm_get_spec: Get a parsed spec — frontmatter, requirements, verify commands, sections.swarm_get_review: Get a parsed review packet — status, coverage rows, verify blocks.
Reconcile & Validate
swarm_scan_task: Reconcile a task in progress against its spec and current worktree diff — surfaces coverage gaps, out-of-scope changes, self-report mismatches.swarm_reconcile_review: Compare a finished review packet against the task, spec, and git diff — surfaces coverage gaps, empty-evidence Pass rows, scope drift, and self-report mismatches.swarm_validate_review_packet: Check a review packet's structure, status fields, and evidence requirements.
Safe-Write Scaffolding (no verdicts, no board modifications)
swarm_scaffold_spec: Create a new specification.swarm_split_task: Split a task by copying scope from an existing one.swarm_scaffold_finding: Promote and scaffold a finding.
Resources & Prompts: Templated URIs expose workspace, status, checks, and individual artifacts; prompts provide contextual stances (implementer, reviewer, evidence rule, finding candidate) to guide agent behavior.
Provides tools for reconciling facts, checking workspace state, scanning tasks, managing reviews, and loading parsed artifacts via the Swarm CLI.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@swarm-mcpwhat evidence is missing?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
suspec-mcp
A thin MCP stdio adapter for shell-less access to Suspec's deterministic checker. Thin is the feature.
It requires checks contract 0.21.0, validates every CLI JSON payload, and preserves ordered reports
and exit status.
Tools
suspec_check
Runs one CLI process over an ordered non-empty array of absolute artifact paths. Frontmatter type:
selects behavior.
Input | Meaning |
| ordered non-empty absolute primary paths |
| absolute spec for task paths or one review |
| optional absolute task companion for one review |
|
|
Spec, task, change-plan, and review inputs receive their CLI checks. Inventory, audit, and research
return checked: false. Missing and unknown types are rejected.
One invocation preserves cross-file checks such as C002. Task paths share one specPath; every task
must name that spec. A review is the only primary when taskPath is present. Invalid companion
pairing produces the CLI's structured refusal with ok: false.
Every artifact result repeats its type. Only the optional final (file set) report has none.
suspec_get_checks
Returns the contract version plus each core check's ID and severity in concise mode. Use
responseFormat: "detailed" for names. The same contract is available at suspec://checks.
Startup and resource reads require exact contract 0.21.0 at exit 0. Resource failure throws instead
of returning an error document as resource content.
Related MCP server: tru8-mcp
Envelope
Every successful adapter invocation returns:
ok: whether the CLI ran and produced a valid payload, not whether diagnostics are clean;source: exact command and exit code;data: validated detailed output or concise projection;optional
note;responseFormat.
ok means the adapter worked, not that the artifact is good. A check with blocking diagnostics
remains ok: true; inspect data.level, diagnostics, and source.exitCode.
CLI exits 0, 1, and 2 belong to the contract. Any other exit is an adapter launch failure.
JSON-shaped stdout does not negotiate a new contract. Structured CLI errors are accepted only at
exit 2.
Install
Requires Node.js 22.6 or newer and a suspec CLI. Neither package is published.
git clone https://github.com/jcosta33/suspec-mcp
cd suspec-mcp
corepack enable
pnpm install --frozen-lockfileConfigure absolute entry points so GUI clients do not depend on shell PATH:
{
"mcpServers": {
"suspec": {
"command": "/absolute/path/to/suspec-mcp/bin/suspec-mcp.js",
"args": ["--suspec-bin", "/absolute/path/to/suspec-cli/bin/suspec.js"]
}
}
}CLI precedence:
Flag | Environment | Default |
|
|
|
Each tool call supplies full artifact paths. The server binds no repository, workspace,
configuration, or store. It is an adapter, not a second product brain.
~/.agents/artifacts/<workspace>/ has no special runtime meaning.
Security
Primary and companion paths must be absolute and contain no control, format, or line-separator characters.
The adapter passes a fixed argument array without a shell.
Only
checkand supported companion or contract flags reach the CLI.Review checks may read local relative evidence receipts linked by the review.
The CLI check surface is read-only.
The server can read any path available to its process. Filesystem permission is the security boundary, not a suggestion. Match process permissions to the client trust boundary or apply OS sandboxing.
Develop
Fixture drift uses the real CLI. Handwritten agreement proves nothing. Set SUSPEC_BIN to an
absolute CLI source path; otherwise a sibling package named suspec-cli may satisfy discovery.
Generation rejects other packages.
export SUSPEC_BIN=/absolute/path/to/suspec-cli/bin/suspec.js
pnpm install
pnpm test:run
pnpm gate
pnpm fixturestest/fixtures/provenance.json records CLI git HEAD, complete dirty-worktree hash, and binary hash.
scripts/generate-fixtures.mjs captures output; tests parse every fixture through
src/suspec/contract.ts. Fixtures are generated, never hand-edited.
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jcosta33/suspec-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server