@sylphx/consultant-mcp
v0.2.2
Published
Beta MCP server for typed SOTA consultation, model fan-out, and judge synthesis for autonomous agents.
Readme
Sylphx Consultant MCP
@sylphx/consultant-mcp is a Beta 0.x Model Context Protocol server that gives autonomous agents a typed, audited path to ask a higher-grade consultant panel for:
- ADR / architecture / design review
- research synthesis
- red-team challenge of a proposed answer
- option comparison and trade-off analysis
The beta design intentionally exposes four thin typed MCP tools backed by one shared deliberation engine. The tool split is an agent-facing product contract; the fan-out, policy, redaction, and judge synthesis are shared implementation.
SOTA family roadmap: docs/roadmap/sota-family-roadmap.md.
Status
Release channel: 0.x beta. The latest public package version is the npm registry value for @sylphx/consultant-mcp.
This is a production-shaped beta package, not a final hosted service. It includes:
- MCP stdio server
- OpenRouter-compatible provider adapter
- mock provider for local tests
- panel fan-out
- judge synthesis
- privacy/budget policy gate
- secret-like redaction
- structured output schemas
- tests and dry-run package verification
Deferred intentionally:
- persistent ledger database
- async queue API
- web UI/admin dashboard
- semantic cache
- organization-level approval workflow
Those belong in the future hosted Consultant Service, not in the first MCP package.
Tools
consultant.review_decision
Use for ADRs, architecture choices, production design reviews, public contracts, migrations, security decisions, and expensive irreversible choices.
consultant.research
Use for research synthesis where the answer needs freshness, source quality, contradictions, and evidence gaps.
consultant.challenge_answer
Use when an agent already has a proposed answer and wants skeptical review before sending or shipping.
consultant.compare_options
Use to compare two or more options against criteria and produce a recommendation.
Configuration
export OPENROUTER_API_KEY="..." # or OPENROUTER_FUSION_API_KEY
export CONSULTANT_PANEL_MODELS="openai/gpt-4.1,anthropic/claude-sonnet-4,google/gemini-2.5-pro"
export CONSULTANT_JUDGE_MODEL="openrouter/fusion"
export CONSULTANT_DEFAULT_MAX_USD="2"
export CONSULTANT_ALLOW_CONFIDENTIAL_EXTERNAL="false"For local deterministic testing:
export CONSULTANT_MOCK=trueInstall and Run
From npm after the protected release workflow publishes the package:
npm install -g @sylphx/consultant-mcp
CONSULTANT_MOCK=true sylphx-consultant-mcpFor local development from source:
npm ci
npm run build:rust
CONSULTANT_MOCK=true sylphx-consultant-mcpMCP clients should launch the binary over stdio:
{
"mcpServers": {
"sylphx-consultant": {
"command": "sylphx-consultant-mcp",
"env": {
"OPENROUTER_API_KEY": "${OPENROUTER_API_KEY}",
"CONSULTANT_DEFAULT_MAX_USD": "2"
}
}
}
}Safety model
- Every request declares or defaults
privacyClass. confidentialis blocked from external providers unless explicitly allowed.- Secret-like strings are redacted before model calls.
- Estimated cost is checked against request and service budget.
- Outputs are structured for downstream agent parsing.
- Provider adapters are replaceable; OpenRouter Fusion is an option, not the core dependency.
Design principle
Prompting is an implementation detail. MCP tools are product contracts for agents, policy, cost control, caching, observability, and evaluation.
Project Control and Publication Proof
This repository dogfoods GroundAtlas through CI. Vendor-neutral project facts live in project.manifest.json; Sylphx-specific governance facts stay in .doctrine/project.json; generated .groundatlas* files plus GroundAtlas JSON/Markdown reports are evidence/navigation only, not source of truth.
Public npm publication is owned by .github/workflows/release.yml: a protected GitHub Actions release workflow that runs npm-locked verification, GroundAtlas release dogfood, npm provenance publish, registry readback, install smoke, tag creation, and GitHub release readback. Local package proof remains npm run verify plus CI evidence; generated .groundatlas* files are not publication proof.
