Skip to main content

Agent and MCP Guide

Partial

Status aligned to .mcp.json as of 2026-03-26.

Configured servers​

No project-scoped MCP servers are currently declared in .mcp.json.

Agent access model​

No project-scoped agent access overrides are currently declared in .mcp.json.

Consistency note​

The repository guidance still points to .mcp.json as the source of truth, but the file is currently empty:

  • mcpServers is empty
  • servers is empty

Any MCP servers you may see in a local Codex or Claude install are user-level configuration, not portable project configuration. Treat that as environment-local state until the repo adds explicit server entries here.

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 page

Next best action

After checking tool access, confirm protocol activation status before documenting feature availability.

Open deployment status