Connect Claude Code in the terminal
Reach this instance's tools from a Claude Code session started in this folder.
The first call reads CONTEXT, and a draft after it raises a dialog you answer.
Before you start
Configuration page
Note
This is done from the command line, not on the configuration page.
Command line
Confirm a client here is handed a pipe rather than an address:
revetly doctor --offline
[SKIP] connect this instance declares no served endpoint, so a client reaches it over a pipe it spawns …
Read the tools that pipe serves:
revetly surface
read from the served tool list, not from source — the same `tools/list` every client's catalogue is answered by
Open this folder in Claude Code:
claude
You should see revetly (as Claude Code shows it)
Ask what CONTEXT already holds on one topic with /revetly-ground.
You should see search_context (as Claude Code shows it)
Ask for a draft with /revetly-draft once the read has answered.
You should see Approve (as Claude Code shows it)
Note
revetly init wrote the .mcp.json a session started here reads, and its
entry reaches the engine inside the running container. A session that starts
with the stack down lists no server at all.
On an instance declaring several projects, a repository that works on one of
them can bind its connection. Copy the revetly entry into that repository's
.mcp.json and add --project NAME right after revetly serve, which ends
the entry's script. Calls naming no project then answer for NAME, writes
included, and a call naming another project is refused. revetly manual show multi-project has the rule.
Troubleshooting
The session lists no server. The stack was down when the session started.
Bring the stack up, then start a new session.The tool list is the engine from before a rebuild. The image bakes the
source in. Reconnect with /mcp after docker compose up -d --build revetly.
Next steps