Agent and MCP Guide
Status aligned to .mcp.json as of 2026-02-18.
Configured servers
| Server | Enabled | Purpose |
|---|---|---|
foundry | true | Contract compile/test/cast/anvil flows |
storacha | true | IPFS/Filecoin storage workflows |
railway | true | Deployment/service operations |
Agent access model
| Agent | Declared access |
|---|---|
cracked-coder | foundry, storacha, railway |
code-reviewer | none |
oracle | miro |
Consistency note
.mcp.json declares oracle -> miro in agentAccess, but miro is not present under servers.
Treat this as configuration drift until either:
miroserver block is added, ororacleaccess list is updated to removemiro.
Safe usage policy
- Prefer local tooling (
bun,forge,cast) for small scoped tasks. - Use MCP when cross-system automation is required.
- Avoid exposing secrets in logs or docs examples.
Which source wins if docs and config disagree?
.mcp.json is the source of truth. Update docs in the same PR that changes MCP config.
Next best action
After checking tool access, confirm protocol activation status before documenting feature availability.
Open deployment status