AI Foundry Desk 0.5.0 — One MCP setup across your agents
One MCP setup, across the agents you use
AI Foundry Desk 0.5.0 introduces a safe, scope-aware way to keep MCP server configuration
consistent. You can discover an existing definition, adopt it once, sync it to selected agents,
enable or disable it globally or for one project, and move it between user and project scope without
manually editing every client.
What this gives you
- One canonical user registry and one optional project registry instead of agent-by-agent drift.
- Native user and project synchronization for Claude Code, Codex, Antigravity, and Grok, native
user synchronization for Hermes, and explicit opt-in Pi support through pinned
pi-mcp-adapter2.31.0. - Project-only disable overrides, so a globally useful server can stay off in a sensitive project.
- Atomic scope moves: AFD creates the destination, reconciles native files, and removes the old
ownership in one transaction. - Redacted discovery and dry-run plans with a content-derived confirmation token.
- Automatic rollback if any required write fails, and stale-plan rejection if an agent changes a
file after preview.
AFD preserves unrelated JSON, TOML, and YAML settings and never copies OAuth or login state.
Secret-like headers and environment values must be references to existing environment variables;
their values are not printed in plans.
Run afd catalog to see the MCP capability of each installed agent and scope. Default all-agent
operations fail closed when an adapter is not proven or consented: Pi requires an explicit
--enable-pi-adapter preview before AFD declares its pinned third-party adapter, and Hermes does
not currently have a stable project-scoped MCP surface. You can
deliberately target the verified subset with --agents.
Start with a preview
afd mcp status --scope effective --project .
afd mcp sync --scope effective --project . --agents claude-code,codex,grok --dry-runReview the paths, hashes, capability blockers, and approval token before applying the same command
with --confirm <plan-token>.