Early Access. Commands and behavior can change between releases.
Add a server
List your servers in anmcp.json file, in the mcpServers shape other MCP clients use:
mcp.json
command and args; a remote one is reached at url. Your next
Architech session loads them. Put servers specific to one repository in the project file. To see
where your running session reads its configuration, use /mcp.
How the model sees the tools
In normal orchestrator and agent sessions, the model sees each direct tool asmcp__<server>__<tool>, for example mcp__docs__search, and calls it like any other tool.
For normal orchestrator and agent sessions, leave out a server’s
exposure field or set it to
"direct". With "codemode" or "deferred", the model in those sessions doesn’t see the
tools. Prime is different: its code helpers can call MCP tools, "codemode" ones included,
without exposing them to the model directly.Manage servers with /mcp
Type /mcp in an Architech session to open the MCP manager. It lists every server you configured,
with its state (for example connected · 4 tools, needs sign-in, failed or disabled), its
exposure and where it’s configured (for example project). Servers that need you come first. If
you have none, it tells you which files to add them to.
Pick a server to act on it:
Sign-in is for remote servers that have no
Authorization header and ask for one when Architech
connects. Architech signs you in with OAuth and stores the credentials for you.
You can also run an action directly:
Leave out the server name and Architech picks the only one that fits, or asks you which one. If a
server fails to connect or needs a sign-in when a session starts, Architech tells you once and
points you to
/mcp.
Where MCP tools are available
Project context
The other thing every session loads from your project:
AGENTS.md / CLAUDE.md.