Click on "Deploy 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., "@yotta-dev-mcp Map the modules and entrypoints in the current repository"
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.
Deterministic local development tools exposed over a stdio MCP server.
Tool | Purpose |
| Map modules, imports and entrypoints in a repository. |
| Build a system model with layer data from the architecture contract. |
| Review dependency rules, boundaries and data ownership with evidence. |
| Build the change impact cone with tests, blast radius and rollback probes. |
| Run the L0-L5 verification ladder and return an evidence ledger. |
| Check files, versions, tool contracts, write gates and seeded-defect counterexamples. |
| Probe or explicitly run optional import-linter / dependency-cruiser / Repomix adapters. |
| Locate symbols and text with bounded results. |
| Compress long logs while keeping errors and head/tail context. |
| Apply deterministic review rules with file, line and evidence. |
| Review only added lines in a unified diff. |
| Inspect installed skills and MCP JSON configuration files. |
| Scan for credentials and high-entropy tokens with redacted evidence. |
| Check manifests, lockfiles, insecure sources and typosquat suspicion. |
| Check version alignment, release files and package metadata. |
| Run whitelisted tests, lint or compile checks; execution is explicit. |
| Plan or create a minimal skill scaffold; dry-run by default. |
| Read |
Tools are read-only by default; run_checks, the L2-L4 policy checks in
verify_change, the test subset in self_test, and run_adapter with
action=run require allow_execute=true. scaffold_skill / workflow_state
require apply=true before writing. Python 3.8+ standard library is sufficient;
no network access is required.
system_model reads an optional .yotta/architecture.json (version 1) that declares
layers, dependency rules, boundaries, data ownership, invariants and risk weights. The
result reports PASS, FAIL or UNKNOWN, lists every unknown that still needs
evidence, and keeps verification levels that were not executed in unverified_claims.
architecture_review then checks that contract: dependency rules, boundary visibility
and data ownership each produce findings with file, line and severity. critical and
high findings fail the review, medium and low stay advisory, and anything that
cannot be decided from the model becomes UNKNOWN instead of a silent pass.
impact_analysis starts from changed_files, a unified diff or target symbols and
walks reverse dependencies into a bounded cone: direct consumers, affected layers,
boundaries, data stores, invariants, mapped tests, an explainable blast radius and
rollback probes. It executes nothing.
verify_change runs the post-change ladder: L0 syntax and contract schema, L1
architecture checks inside the impact cone, L2-L4 whitelisted checks declared in
.yotta/verification.json with explicit allow_execute=true, and L5 independent
review kept as unverified work. Ledger entries carry a claim, status, evidence,
check name and output hash so the result can be recomputed; skipped levels are never
written as passing.
self_test checks the integrity of yotta-dev-mcp itself: required files, version
alignment across package / SKILL / CHANGELOG / server / engine, protocol tool schema
drift, fail-closed write gates, and seeded-defect plus mutation controls that prove
the verifier turns red or unknown. The test suite is not executed by default.
run_adapter is an optional enhancement layer. action=list only probes the
project-local node_modules/.bin, project virtualenvs and PATH; action=run
requires allow_execute=true and runs one fixed adapter command. Missing tools,
missing config, invalid output and timeouts return UNKNOWN with a next step.
No package is installed or downloaded, and adapter results do not silently change
the status of the core architecture tools. Details: references/adapters.md.
Schema, glob rules, finding codes and cone fields: references/architecture-contract.md.
Related MCP server: erbina
npx -y @yottameta/yotta-dev-mcpnpx -y @yottameta/yotta-dev-mcp --agent codex
npx -y @yottameta/yotta-dev-mcp --dir <skill-directory>
npx -y @yottameta/yotta-dev-mcp --listThe installer uses explicit targets. --global additionally requires --yes, and
--dry-run prints the target without writing.
Other installation methods:
git clone https://github.com/YottaMeta/yotta-dev-mcp.git <skill-directory>/yotta-dev-mcp
bash <skill-directory>/yotta-dev-mcp/install.sh --agent codexYou can also use GitHub's Download ZIP action and unpack the archive into the skill directory.
The engine can also be used without MCP:
python scripts/dev_engine.py repo-map .
python scripts/dev_engine.py system-model .
python scripts/dev_engine.py architecture-review .
python scripts/dev_engine.py impact-analysis . --changed src/core/store.py
python scripts/dev_engine.py verify-change . --changed src/core/store.py
python scripts/dev_engine.py verify-change . --changed src/core/store.py --level L2 --allow-execute
python scripts/dev_engine.py self-test .
python scripts/dev_engine.py adapter . --action list
python scripts/dev_engine.py adapter . --action run --adapter dependency-cruiser --allow-execute
python scripts/dev_engine.py find-code . "helper"
python scripts/dev_engine.py review-code .
python scripts/dev_engine.py mcp-doctorNo code execution, no automatic edits, no commits.
No network access, no package-existence lookup.
Static deterministic findings only; human review remains the final decision.
0.2.1 (2026-09-25) is a defect-fix release: mcp_doctor now covers Codex,
WorkBuddy, OpenCode, Cursor and other hosts with a coverage report;
self_test(mode="installed") is distribution-aware; repo_map resolves
from . import X; scan_secrets filters path/hash/filename noise; and
review_code ignores temporary directories.
0.2.0 (2026-09-25) adds system_model, architecture_review,
impact_analysis, verify_change, self_test, run_adapter, and the
.yotta/architecture.json plus optional .yotta/verification.json contracts on
top of the twelve deterministic tools.
This server cannot be deployed
327 dev tools via REST API and MCP. Generate Dockerfiles, schemas, K8s, APIs, and more.
Self-hosted MCP server: 26 deterministic dev, security, and EVM tools.
Pre-flight MCP security. Blocks compromised deps + tool drift. HMAC-signed. Dredd judges.
Generate a typed SDK, CLI, and MCP server from any OpenAPI or GraphQL spec, and keep them current.
