Assure la gouvernance de l'architecture exécutable en validant les ensembles de règles et l'historique des ADR via une passerelle pilotée par l'IA.
Aussi connu sous beyondnetcode/evolith_arch32, evolith, @beyondnet/evolith-mcp
- Étoiles
- 2
- Outils
- 55
- Téléchargements, 30 jours
- 244
- Dernière version
- 1.3.3
- Dernier commit
- 1 nov. 2026
- Licence
- MIT
Qu'est-ce que Evolith Architecture Governance MCP ?
Evolith Architecture Governance est un serveur MCP. Assure la gouvernance de l'architecture exécutable en validant les ensembles de règles et l'historique des ADR via une passerelle pilotée par l'IA. Il expose 55 outils, comme evolith-validate, evolith-composable-validate, evolith-evaluate.
Résumé généré à partir du README du projet
À propos du MCP server Evolith Architecture Governance
Evolith Architecture Governance fournit une passerelle pour appliquer des règles d'architecture exécutables et valider l'historique des ADR via une interface pilotée par l'IA. Il fonctionne comme un MCP server de premier ordre qui communique directement avec la couche de logique métier evolith-core, plutôt que de s'appuyer sur des sous-processus CLI. Cela permet aux agents IA d'interagir directement avec les contraintes architecturales et l'état des dépôts.
Les développeurs peuvent déployer ce serveur en utilisant stdio pour les agents locaux comme Cursor ou Claude Desktop, ou via streamable HTTP pour des intégrations distantes et évolutives. Lors de l'utilisation du transport HTTP, le serveur impose une authentification obligatoire dans les environnements de production via des clés API ou des jetons Bearer JWT. Il dispose également d'un modèle ABAC sophistiqué qui restreint l'accès aux outils en fonction des rôles de l'utilisateur (développeur, opérateur ou architecte), garantissant que les opérations sensibles comme le déploiement sont bloquées en production pour les utilisateurs non autorisés.
Au-delà de la simple validation, le serveur gère des workflows complexes en utilisant une validation humaine (human-in-the-loop) pour les opérations mutatives. Il utilise un mécanisme d'état de requête pour garantir que les approbations des actions modifiant l'état sont sécurisées et liées à des principaux et des tenants spécifiques.
Ce que vous pouvez faire avec
- 1Valider les ensembles de règles architecturalesUn agent IA peut vérifier si un chemin de dépôt spécifique est conforme aux règles architecturales et à la configuration définies.
- 2Auditer l'historique des ADRUn développeur peut utiliser l'agent pour vérifier l'historique des Architecture Decision Records et l'état de la phase actuelle dans Git.
- 3Sécuriser les opérations modifiant l'étatLe serveur exige une approbation humaine pour les outils mutatifs en utilisant un état de requête scellé.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer Evolith Architecture Governance MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller Evolith Architecture Governance MCP dans Claude Code
$ claude mcp add evolith -- npx -y @beyondnet/evolith-mcpInstaller Evolith Architecture Governance MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"evolith": {
"command": "npx",
"args": [
"-y",
"@beyondnet/evolith-mcp"
]
}
}
}Installer Evolith Architecture Governance MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"evolith": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@beyondnet/evolith-mcp"
]
}
}
}Installer Evolith Architecture Governance MCP dans VS Code CLI
$ code --add-mcp '{"name":"evolith","type":"stdio","command":"npx","args":["-y","@beyondnet/evolith-mcp"]}'Installer Evolith Architecture Governance MCP dans Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"evolith": {
"command": "npx",
"args": [
"-y",
"@beyondnet/evolith-mcp"
]
}
}
}Installer Evolith Architecture Governance MCP dans Codex
$ codex mcp add evolith -- npx -y @beyondnet/evolith-mcpInstaller Evolith Architecture Governance MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.evolith] command = "npx" args = ["-y", "@beyondnet/evolith-mcp"]
Installer Evolith Architecture Governance MCP dans Gemini CLI
$ gemini mcp add -s user evolith npx -- -y @beyondnet/evolith-mcpInstaller Evolith Architecture Governance MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"evolith": {
"command": "npx",
"args": [
"-y",
"@beyondnet/evolith-mcp"
]
}
}
}Outils MCP Evolith Architecture Governance 55
Détectés depuis le READMEevolith-validateevolith-composable-validateevolith-evaluateevolith-ruleset-listevolith-architecture-validateevolith-drift-detectevolith-topology-recommendevolith-phase-artifacts-evaluateevolith-pattern-listevolith-pattern-getevolith-pattern-list-by-topologyevolith-topology-list
| evolith-validate | — | |
| evolith-composable-validate | — | |
| evolith-evaluate | — | |
| evolith-ruleset-list | — | |
| evolith-architecture-validate | — | |
| evolith-drift-detect | — | |
| evolith-topology-recommend | — | |
| evolith-phase-artifacts-evaluate | — | |
| evolith-pattern-list | — | |
| evolith-pattern-get | — | |
| evolith-pattern-list-by-topology | — | |
| evolith-topology-list | — |
Afficher les 55 outilsAfficher moins d'outils
evolith-topology-getevolith-gate-evaluateevolith-phase-advanceevolith-sdlc-statusevolith-sdlc-handoffevolith-dora-metricsevolith-sdlc-generateevolith-moscow-createevolith-moscow-loadevolith-moscow-updateevolith-moscow-removeevolith-moscow-listevolith-moscow-validateevolith-moscow-reportevolith-adr-listevolith-adr-getevolith-adr-matrixevolith-adr-createevolith-adr-updateevolith-agent-installevolith-agent-listevolith-agent-validateevolith-agent-upgradeevolith-agent-removeevolith-agent-runevolith-satellite-listevolith-satellite-statusevolith-satellite-createevolith-satellite-adoptevolith-init-batchevolith-scaffoldevolith-docs-scaffoldevolith-fixturesevolith-upgrade-planevolith-upgrade-applyevolith-knowledge-searchevolith-auto-fixevolith-config-getevolith-config-setevolith-metricsevolith-historyevolith-profileevolith-standards
| evolith-topology-get | — | |
| evolith-gate-evaluate | — | |
| evolith-phase-advance | — | |
| evolith-sdlc-status | — | |
| evolith-sdlc-handoff | — | |
| evolith-dora-metrics | — | |
| evolith-sdlc-generate | — | |
| evolith-moscow-create | — | |
| evolith-moscow-load | — | |
| evolith-moscow-update | — | |
| evolith-moscow-remove | — | |
| evolith-moscow-list | — | |
| evolith-moscow-validate | — | |
| evolith-moscow-report | — | |
| evolith-adr-list | — | |
| evolith-adr-get | — | |
| evolith-adr-matrix | — | |
| evolith-adr-create | — | |
| evolith-adr-update | — | |
| evolith-agent-install | — | |
| evolith-agent-list | — | |
| evolith-agent-validate | — | |
| evolith-agent-upgrade | — | |
| evolith-agent-remove | — | |
| evolith-agent-run | — | |
| evolith-satellite-list | — | |
| evolith-satellite-status | — | |
| evolith-satellite-create | — | |
| evolith-satellite-adopt | — | |
| evolith-init-batch | — | |
| evolith-scaffold | — | |
| evolith-docs-scaffold | — | |
| evolith-fixtures | — | |
| evolith-upgrade-plan | — | |
| evolith-upgrade-apply | — | |
| evolith-knowledge-search | — | |
| evolith-auto-fix | — | |
| evolith-config-get | — | |
| evolith-config-set | — | |
| evolith-metrics | — | |
| evolith-history | — | |
| evolith-profile | — | |
| evolith-standards | — |
Configuration
EVOLITH_API_KEYLOG_LEVELNODE_ENVOTEL_EXPORTER_OTLP_ENDPOINTOTEL_SERVICE_NAME
| Nom | Description | Type |
|---|---|---|
| EVOLITH_API_KEY | — | |
| LOG_LEVEL | — | |
| NODE_ENV | — | |
| OTEL_EXPORTER_OTLP_ENDPOINT | — | |
| OTEL_SERVICE_NAME | — |
Vérifications automatisées
Exécuté le 12 nov. 2026Rapport complet →A passé nos vérifications automatisées. Il ne s'agit pas d'un audit de sécurité : lisez le code et donnez au serveur l'accès le plus restreint dont il a besoin. Fonctionnement des vérifications
- Dépôt source lié et accessibleRéussi
- Licence open source (OSI)Réussi
- Commit ou version publiée au cours de l'année écouléeRéussi
- Nom du package non proche d'un package populaireRéussi
- L'endpoint distant utilise HTTPSNon vérifié
- Les outils destructifs sont étiquetésRéussi
- Aucune instruction cachée destinée au modèleRéussi
- Aucun avis critique dans le package ou ses dépendancesRéussi
README
Voir sur GitHub@beyondnet/evolith-mcp
Evolith MCP Gateway — First-Class Model Context Protocol Server
Bilingual navigation: Versión en Español
Decouples the MCP server from the CLI. It is a first-class product that exposes the MCP tools as a Gateway talking to @beyondnet/evolith-core (the reusable business-logic layer), instead of shelling out to CLI subprocesses.
Table of contents
- Architecture diagram
- Transports
- Installation and configuration
- Authentication
- Available tools (55)
- Available resources (12 + dynamic)
- Available prompts (8)
- Mutative operations
- Internal architecture
- Agent use cases
- Client configuration
- SmartCLI integration
- Extension guide
- Observability
- Good practices
- Troubleshooting
Architecture diagram
sequenceDiagram
participant Agent as "AI Agent<br/>(Cursor, Claude Desktop, Custom)"
participant Gateway as "MCP Gateway<br/>@beyondnet/evolith-mcp"
participant Core as "Business Logic<br/>@beyondnet/evolith-core"
participant FS as "File System"
participant Git as "Git"
Note over Agent,Gateway: Transport: stdio (local) or Streamable HTTP (remote)
Agent->>+Gateway: tools/call { name: "evolith-validate", args: { path: "/repo" } }
Gateway->>Gateway: 1. Generate correlationId (evl-xxx)
Gateway->>Gateway: 2. Lookup tool in ToolRegistry
Gateway->>Gateway: 3. ABAC authorization check
Gateway->>Gateway: 4. Start timing + structured log (Pino)
Gateway->>+Core: ValidateSatelliteUseCase.execute({ satellitePath })
Core->>+FS: Read evolith.yaml, rulesets/
FS-->>-Core: Configuration + rule definitions
Core->>+Git: Check ADR history, phase state
Git-->>-Core: Phase & commit data
Core->>Core: Evaluate rules (Native + OPA)
Core-->>-Gateway: ValidationResult { status, issues }
Gateway->>Gateway: 5. Wrap in SuccessEnvelope { success, data, meta }
Gateway->>Gateway: 6. Audit log + completion duration
Gateway-->>-Agent: { content: [{ type: "text", text: "{...}" }] }
Note over Agent,Gateway: All errors wrapped in ErrorEnvelope with EvolithErrorCode
Transports
| Transport | Use | Command |
|---|---|---|
| stdio (JSON-RPC 2.0) | Local agents, Cursor, Claude Desktop | evolith-mcp serve |
| Streamable HTTP (official MCP SDK) | Remote agents, scalability | evolith-mcp serve --transport http --port 49100 |
The default port is
3000(main.ts: envPORTor--port, falling back to3000). The49100used in the examples is an arbitrary value, not the default.Logs are always written to stderr (Pino), because stdout is reserved for the JSON-RPC stream of the stdio transport.
Installation and configuration
Installation
# From the monorepo
npm install @beyondnet/evolith-mcp
# Or globally
npm install -g @beyondnet/evolith-mcp
Usage
# stdio (default) — for Cursor, Claude Desktop, etc.
evolith-mcp serve
# HTTP — for remote integration
evolith-mcp serve --transport http --port 49100
Environment variables
| Variable | Default | Description |
|---|---|---|
TRANSPORT |
stdio |
Active transport: stdio or http |
PORT |
3000 |
Port for the HTTP transport |
MCP_HTTP_HOST |
0.0.0.0 |
Bind host of the HTTP server. Use 127.0.0.1 for local-only |
EVOLITH_API_KEY |
— | API key for authentication on the HTTP transport |
EVOLITH_MCP_ALLOW_NO_AUTH |
false |
HTTP only. Allows HTTP to start without an API key (non-production only). Ignored in production and on stdio (which warns at startup) |
JWT_SECRET |
— | Optional secret used to validate a Bearer JWT (HS256) in addition to the API key |
NODE_ENV |
development |
In production, HTTP auth is mandatory |
LOG_LEVEL |
info |
Pino log level: trace, debug, info, warn, error |
REDIS_URL |
— | Redis URL for the resource cache (e.g. redis://localhost:6379). The cache is optional. |
OTEL_EXPORTER_OTLP_ENDPOINT |
— | OpenTelemetry endpoint for tracing |
OTEL_SERVICE_NAME |
evolith-mcp |
Service name used in the traces |
EVOLITH_MCP_REQUEST_STATE_SECRET |
— | Key that seals the MRTR requestState (2026-07-28 path). Falls back to EVOLITH_API_KEY, then JWT_SECRET, then a per-process key. Set it explicitly whenever more than one replica is served, or an approval retry landing on another replica is rejected |
EVOLITH_MCP_RESOURCE_AUTH_SERVERS |
— | Comma-separated authorization server issuers published in the Protected Resource Metadata document. Defaults to EVOLITH_MCP_OAUTH_ISSUER |
EVOLITH_MCP_RESOURCE_URI |
request host | Canonical URI of this server (RFC 8707 resource identifier) published as resource |
EVOLITH_MCP_RESOURCE_SCOPES |
read write |
Scopes published as scopes_supported and challenged in WWW-Authenticate |
The binary also accepts the flags
--transport/-t,--port/-p,--api-keyand--allow-no-auth(HTTP only), as well as theevolith-mcp versionsubcommand.
Authentication
stdio transport
No request authentication is required: the process is local, single-user, and the agent runs it directly. The transport establishes an explicit local session principal (id=local-stdio-session, role=local-session, roles=[local-session, operator], scopes=[read, write]) that is recorded in the audit trail of every call (GT-572).
This is not an authorization bypass: ABAC (native + OPA) is still evaluated on every tools/call with that identity, the deploy tools are still denied in production (they require architect), and every mutative tool still demands the HITL gate { apply, approvalToken }. --allow-no-auth / EVOLITH_MCP_ALLOW_NO_AUTH do not apply to stdio (there is no request authentication to skip); if they are passed together with --transport stdio, the server warns about it on stderr at startup.
HTTP transport
In production (NODE_ENV=production), authentication is mandatory: validateAuth() ignores EVOLITH_MCP_ALLOW_NO_AUTH and rejects every request without a valid credential (401). The value of EVOLITH_API_KEY is an arbitrary secret (any string; no prefix required) compared by equality. It is accepted in either of these two headers:
Authorization: Bearer <EVOLITH_API_KEY>
x-api-key: <EVOLITH_API_KEY>
/health is public (a liveness probe) and requires no credential.
When an OAuth issuer is configured, /.well-known/oauth-protected-resource (and the path-inserted /.well-known/oauth-protected-resource/<path>) is also public: it is the RFC 9728 document an unauthenticated client reads to discover which authorization server to go to, so gating it behind the credential it is trying to obtain would make discovery impossible. It carries no MCP data — only the issuer, the resource identifier and the scope names. A 401 from a protected resource additionally carries a WWW-Authenticate: Bearer resource_metadata="…", scope="…" challenge, which is the discovery mechanism MCP clients must prefer. Without an issuer the endpoint returns 404 rather than publishing a document with an empty authorization_servers.
Client registration never flows through this server: it is a resource server, and the 2026-07-28 revision has clients obtain a client_id from a Client ID Metadata Document (or pre-registration) at the authorization server. Dynamic Client Registration is deprecated and is not implemented here; protected-resource-metadata.spec.ts fails the build if a registration endpoint is ever introduced.
Protocol revisions
The server answers two protocol revisions on the same HTTP endpoint:
| Revision | How a request selects it | Shape |
|---|---|---|
2026-07-28 (current) |
_meta["io.modelcontextprotocol/protocolVersion"] on every request, or a server/discover call |
Stateless. No initialize, no notifications/initialized, no Mcp-Session-Id. Every result carries resultType; the approval gate is expressed as an InputRequiredResult with a sealed requestState (MRTR) |
2025-11-25 |
an initialize request |
The handshake-based path served by @modelcontextprotocol/sdk, which mints and requires Mcp-Session-Id |
Both revisions run through one dispatch, so ABAC (native + OPA), the scope gate, the approval gate and the audit trail are the same code on either path. The 2025-11-25 path is retained because the published SDK still declares it as its latest revision; it is not an alternative design.
On the 2026-07-28 path a state-changing tool answers resultType: "input_required" with an elicitation/create request and an opaque requestState. The client gathers the human's approval and retries the original call — new JSON-RPC id, same parameters, plus requestState and inputResponses. The requestState is sealed with AES-256-GCM and bound to the principal, the tenant, the originating call and a short TTL, so it cannot be replayed across users, calls or time. A caller that already holds an approval may still pass { apply: true, approvalToken } inline and skip the round trip, exactly as on the 2025-11-25 path.
The
ApiKeyProvisioningService(below) is an advanced and optional mechanism for issuing keys with anevk_prefix, a SHA-256 hash and a TTL. It is independent of the startupEVOLITH_API_KEYdescribed here.
API key provisioning
The ApiKeyProvisioningService manages the lifecycle of the keys:
| Operation | Description |
|---|---|
generateKey(label, options) |
Generates a key with an evk_ prefix, a SHA-256 hash and a configurable TTL (90 days by default) |
validateKey(rawKey) |
Validates the key against the stored hash and checks expiry |
rotateKey(keyId) |
Revokes the current key and generates a new one for the same client |
revokeKey(keyId) |
Revokes a key immediately |
Keys carry scopes: read, write, admin. They are bound to a tenant.
ABAC model
The AbacEvaluator controls which tools each user may invoke, based on their roles:
| Tool type | Allowed roles | Environment |
|---|---|---|
| Read (list, get, status) | Every authenticated role | Any |
| Write (fix, install, set) | operator, sre, architect, admin |
Any |
| Write | developer, qa |
Non-production only |
| Deploy (deploy, publish, merge) | architect, admin, operator, sre |
Any |
| Deploy | Anyone except architect |
Blocked in production |
ABAC codes:
| Code | Cause |
|---|---|
ABAC-01 |
Tool denied for the user's role/environment |
ABAC-02 |
User with no roles — every tool is denied |
ABAC-03 |
Tool not classified into any known group |
Tool classification (substring heuristic). The internal role sets are DEVELOPER = {developer, qa}, OPERATOR = {operator, sre} and ARCHITECT = {architect, admin}. The read/write/deploy classification of each tool is a heuristic over its name (abac-evaluator.ts): it counts as read if the name contains read/list/get (or does not begin with evolith-); as write if it contains write/replace/run/fix/advance; as deploy if it contains deploy/publish/merge. Because of that heuristic, evolith-phase-advance is classified as write (the advance substring), even though it only proposes the transition. A tool that fits no group is rejected with ABAC-03.
Authentication precedence (HTTP). The guard (mcp-server-auth.ts) evaluates the API key first: if the Authorization: Bearer <token> or the x-api-key header matches EVOLITH_API_KEY, it grants an admin context (role admin, every tool allowed). Only if the key does not match and JWT_SECRET is defined does it try to validate the Bearer as a JWT HS256; in that case the roles in the JWT payload are what feed ABAC. /health is public. In production, auth is mandatory (it ignores EVOLITH_MCP_ALLOW_NO_AUTH).
Available tools (55)
The tools are obtained at runtime via tools/list. All of them return raw data, which the Gateway wraps in a SuccessEnvelope or an ErrorEnvelope.
The count is derived from the registration sources by the generated Product Surface Inventory (
tools/*.ts,resources.service.ts,prompts.service.ts); the tables below name every tool, grouped by area. When they disagree,tools/listand the inventory win.
Validation
| Tool | Description | Mutative |
|---|---|---|
evolith-validate |
Validates a repository against the Evolith governance rules (GOV, INH, ACL, OCB) | No |
evolith-composable-validate |
Combinable multi-mode validation: SDLC, Architecture, Ruleset, ADR, Ad-hoc | No |
evolith-composable-validate schema:
{
"path": "string (required) — path to the satellite repository",
"corePath": "string — path to the Evolith Core",
"engine": "'native' | 'opa' — evaluation engine (default: native)",
"topology": "'modular-monolith' | 'microservices' | 'serverless' | ... — enables Architecture mode",
"phase": "'discovery' | 'design' | 'construction' | 'qa' | 'release' — enables SDLC mode (the schema also accepts the legacy aliases 'f1'..'f5', deprecated)",
"ruleset": "string — enables Ruleset mode",
"adr": "'adr-0002' | 'adr-0005' | 'adr-0010' | ... — enables ADR mode",
"file": "string — enables Ad-hoc mode over a single file"
}
Modes are enabled by combining fields. Several of them can be used in a single call.
Evaluation (ADR-0101)
| Tool | Description | Mutative |
|---|---|---|
evolith-evaluate |
Evaluates a canonical EvaluationContext (gates, artifacts, rules, compliance) and returns an EvaluationResult in the ADR-0073 envelope. Stateless: product, tenant and initiative are opaque context |
No |
evolith-ruleset-list |
Lists the ruleset packs this Core can evaluate — the canonical refs accepted by evolith-validate's select, with the rule count per pack |
No |
Architecture
| Tool | Description | Mutative |
|---|---|---|
evolith-architecture-validate |
Validates a satellite project against the architecture rules | No |
evolith-drift-detect |
Detects drift between the declared architecture and the real one | No |
evolith-topology-recommend |
Recommends a topology composition from technical signals (advisory, ADR-0104): the Core recommends, the tenant confirms | No |
evolith-phase-artifacts-evaluate |
Measures downstream-phase artifact completeness for a confirmed topology composition (advisory, ADR-0104) | No |
Patterns
| Tool | Description | Mutative |
|---|---|---|
evolith-pattern-list |
Lists the canonical patterns and anti-patterns (PAT-NNNN), optionally filtered by category, kind or applicable topology |
No |
evolith-pattern-get |
Gets one pattern by id: problem, forces, solution, applicability per topology, governing ADRs | No |
evolith-pattern-list-by-topology |
Lists the patterns that apply to a topology, how strongly (required → recommended → optional) and which rules each one imposes | No |
Topologies
| Tool | Description | Mutative |
|---|---|---|
evolith-topology-list |
Lists every architecture topology available in Evolith Core | No |
evolith-topology-get |
Gets the full manifest of a topology by ID | No |
evolith-topology-list schema:
{
"corePath": "string — path to the Core (optional, default: ../evolith)"
}
evolith-topology-get schema:
{
"id": "string (required) — topology ID (e.g. modular-monolith)",
"corePath": "string — path to the Core (optional)"
}
Available topologies: modular-monolith, distributed-modules, microservices, serverless, edge-computing, event-driven, data-mesh, agentic-ai
SDLC gates
| Tool | Description | Mutative |
|---|---|---|
evolith-gate-evaluate |
Evaluates a specific SDLC phase gate | No |
evolith-phase-advance |
Proposes a phase transition | No¹ |
¹
evolith-phase-advanceonly proposes the transition — it does not execute it. Executing it is the responsibility of the operator or of the Tracker.
SDLC
| Tool | Description | Mutative |
|---|---|---|
evolith-sdlc-status |
Gets the current SDLC phase state of the repository | No |
evolith-sdlc-handoff |
Runs the phase handoff, generating the evidence manifest | Yes |
evolith-dora-metrics |
Approximates DORA metrics from the Git history: deployment frequency, lead time (approx.), total and merge commits within the window (days, default 90) |
No |
evolith-sdlc-generate |
Generates a Hexagonal Architecture scaffold from a Mermaid classDiagram in a Markdown DDD model (parity with sdlc generate) |
Yes |
MoSCoW
| Tool | Description | Mutative |
|---|---|---|
evolith-moscow-create |
Creates a MoSCoW matrix for a phase of the project | Yes |
evolith-moscow-load |
Loads an existing MoSCoW matrix | No |
evolith-moscow-update |
Updates items in the MoSCoW matrix | Yes |
evolith-moscow-remove |
Removes items from the matrix | Yes |
evolith-moscow-list |
Lists the MoSCoW matrices of the project | No |
evolith-moscow-validate |
Validates that the matrix is well formed | No |
evolith-moscow-report |
Generates a MoSCoW prioritization report | No |
² The three MoSCoW tools that write to
.evolith/moscow/{phase}.json(create,update,remove) declaremutative: trueinmoscow.tools.tssince 2026-07-11, so the dispatcher demandsapply/approvalTokenfor them;load,list,validateandreportare reads.
ADRs
| Tool | Description | Mutative |
|---|---|---|
evolith-adr-list |
Lists every Architecture Decision Record (id, title, status, date) | No |
evolith-adr-get |
Gets the full details of one ADR by id (ADR-0001) or number |
No |
evolith-adr-matrix |
Gets the ADR matrix summary (totals by status, recent ADRs) | No |
evolith-adr-create |
Creates an ADR: writes reference/architecture/adrs/<id>.md and updates the matrix |
Yes |
evolith-adr-update |
Updates the status of an ADR (Proposed, Accepted, Deprecated, Superseded, Amended) | Yes |
Agents
| Tool | Description | Mutative |
|---|---|---|
evolith-agent-install |
Installs an Evolith agent in the repository | Yes |
evolith-agent-list |
Lists the installed agents | No |
evolith-agent-validate |
Validates the configuration of an agent | No |
evolith-agent-upgrade |
Upgrades an agent to the latest version of the template | Yes |
evolith-agent-remove |
Removes an agent from the repository | Yes |
evolith-agent-run |
Runs an intent through the Agent Runtime pipeline | Yes |
Satellites
| Tool | Description | Mutative |
|---|---|---|
evolith-satellite-list |
Lists the registered satellites from the local satellite-registry.json |
No |
evolith-satellite-status |
Gets the status and details of a registered satellite by id | No |
evolith-satellite-create |
Creates a satellite repository on GitHub and registers it (ADR-0073 envelope) | Yes |
evolith-satellite-adopt |
Adopts an existing GitHub repository as a satellite (ADR-0073 envelope) | Yes |
Scaffolding and initialization
| Tool | Description | Mutative |
|---|---|---|
evolith-init-batch |
Non-interactive (batch/CI) initialization of a satellite; parity with init --config <json> / init --yes, without prompts |
Yes |
evolith-scaffold |
Scaffolds a satellite along the progressive maturity axis (phase 1 modular-monolith → 2 distributed-modules → 3 microservices) | Yes |
evolith-docs-scaffold |
Scaffolds the base documentation Evolith requires (README.md, AGENTS.md, MASTER_INDEX.md, evolith.yaml); mirrors the docs command |
Yes |
evolith-fixtures |
Seeds reproducible fixtures and sample data (evolith.yaml, ADRs, rulesets) for demos and tests |
Yes |
Upgrades
| Tool | Description | Mutative |
|---|---|---|
evolith-upgrade-plan |
Plans a satellite upgrade against the upstream Core (dry-run): change plan, breaking changes, estimated risk, nothing written | No |
evolith-upgrade-apply |
Applies a satellite upgrade from the upstream Core; upstream-only changes are written, local-only changes never are | Yes |
Knowledge
| Tool | Description | Mutative |
|---|---|---|
evolith-knowledge-search |
Searches the architecture knowledge corpus (ADRs, rulesets, standards) with BM25-first hybrid retrieval; ranked chunks with citations | No |
Remediation
| Tool | Description | Mutative |
|---|---|---|
evolith-auto-fix |
Applies automatic fixes to the detected violations | Yes |
Configuration
| Tool | Description | Mutative |
|---|---|---|
evolith-config-get |
Gets configuration values from evolith.yaml |
No |
evolith-config-set |
Updates values in evolith.yaml |
Yes |
Observability
| Tool | Description | Mutative |
|---|---|---|
evolith-metrics |
Returns internal MCP Gateway metrics (calls, latency, errors) | No |
CLI parity reads (GT-682)
Three CLI commands that had no MCP counterpart, ported as read-only tools over the CLI's own readers in core-domain. Their write modes (history --clear/--replay, profile create/switch/delete, standards --init/--validate/--export) stay on the CLI.
| Tool | Description | Mutative |
|---|---|---|
evolith-history |
Reads the CLI command history ($HOME/.evolith/history.jsonl): list, get, search, stats |
No |
evolith-profile |
Reads the CLI profile store: current (active profile and its values) or list |
No |
evolith-standards |
Reads the standards under <path>/reference/standards: list (optional category) or get |
No |
Available resources (12 + dynamic)
Resources are obtained via resources/list and read via resources/read.
Static resources (resources/list)
| URI | Name | Description |
|---|---|---|
evolith://rulesets |
Rulesets | Lists every ruleset of Evolith Core |
evolith://phase-gates |
Phase Gates | Definitions and requirements of the phase gates |
evolith://agents |
Agents | List of installed Evolith agents |
evolith://core/info |
Core Info | General Core information (version, total rulesets, capabilities) |
evolith://governance/version |
Governance Version | Version of the governance schema |
evolith://core/version |
Core Version | Version of the Core schema |
evolith://repository/config |
Repository Config | Contents of the current repository's evolith.yaml |
evolith://moscow/phase-0 |
MoSCoW Phase 0 | MoSCoW matrix for the discovery phase |
evolith://architecture/topologies |
Architecture Topologies | List of every available topology |
evolith://architecture/patterns |
Architecture Patterns | Canonical patterns and anti-patterns (PAT-NNNN) with their applicability and enforcing rules |
evolith://capabilities |
Capability Manifest | Versioned capability manifest of the evaluation engine (evaluationKinds, engines, surfaces, supportedConsumers) |
evolith://contracts |
Machine Contracts | Machine-readable schema/contract set the Core publishes for external consumers |
Questions sur Evolith Architecture Governance MCP
Comment ajouter Evolith Architecture Governance MCP à Claude Code ?
Exécutez claude mcp add evolith -- npx -y @beyondnet/evolith-mcp dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter Evolith Architecture Governance MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Quels outils Evolith Architecture Governance MCP fournit-il ?
Il expose 55 outils, dont evolith-validate, evolith-composable-validate, evolith-evaluate, evolith-ruleset-list, evolith-architecture-validate.
Quels transports le serveur prend-il en charge ?
Le serveur prend en charge stdio pour les agents locaux comme Cursor ou Claude Desktop, ainsi que le streamable HTTP pour l'intégration à distance et la scalabilité.