MCP relocation
Moving rarely-used MCP servers out of the loaded tool list and into a CLI, without losing them.
Every MCP server registered with Claude Code contributes its tool definitions to the context of every session, whether you call them or not. A handful of servers is a meaningful standing cost.
CULP moves eligible servers out of Claude's loaded configuration and into
private mcp-cli config files under ~/.culp/mcp/. They stay available; they
stop being loaded.
Nothing disappears
The original registrations are written to disk before they are moved. One command puts them back the way they were.
The session is told which servers were relocated and, for each, the tools it exposes: the name, one line of description, and the required argument names.
A relocated server that Claude has never heard of is a server Claude will never plan around. Naming the tools is what keeps them usable, and leaving out the JSON schemas is what keeps that cheap.
Calling one
Through mcp-cli, from Bash or PowerShell. The session start message prints the
exact command lines with the right config file already filled in.
One rule matters and the message repeats it: every option must follow the
subcommand. An option placed before it is discarded, and mcp-cli then silently
loads its own bundled server inventory instead of yours.
What it costs
The tool catalogue is discovered once and cached, keyed by the content of your configuration, with a per-server timeout and a total startup budget. A server that fails to answer is remembered as having failed, so it is not retried on every session start.