Installs read-only and trusted-write MCP client config examples under /usr/local/share/clawdie-iso/mcp-examples and links them from the bootstrap page.\n\nChecks: ./scripts/check-format.sh; sh -n build.sh scripts/stage-colibri-iso.sh; python3 -m json.tool MCP examples; git diff --check |
||
|---|---|---|
| .. | ||
| mcp-readonly.json | ||
| mcp-trusted-write.json | ||
| README.md | ||
Colibri MCP client examples
The live USB includes /usr/local/bin/colibri-mcp, an MCP server that exposes
Colibri status, glasspane snapshots, task lists, and skills to MCP-capable
editors/assistants.
Default posture is read-only. Write tools are available only when the MCP server
process is launched with COLIBRI_MCP_WRITE=1.
Generic MCP client config
Most MCP clients accept a config shaped like mcpServers. Use one of:
mcp-readonly.json— safe default profilemcp-trusted-write.json— explicit trusted profile with write tools enabled
Quick checks
colibri-mcp tools
COLIBRI_MCP_WRITE=1 colibri-mcp tools
colibri-mcp socket-path
Claude Code example
If your Claude Code version supports claude mcp add, adapt:
claude mcp add colibri /usr/local/bin/colibri-mcp
claude mcp add colibri-write --env COLIBRI_MCP_WRITE=1 /usr/local/bin/colibri-mcp
If your version uses a JSON config file instead, copy the matching object from
mcp-readonly.json or mcp-trusted-write.json.
Zed / Cursor example
Zed, Cursor, and other MCP-capable editors may use slightly different config file paths or wrapper keys by version. The server object is the important part:
{
"command": "/usr/local/bin/colibri-mcp",
"args": [],
"env": {}
}
For a write-capable profile, add:
{
"env": { "COLIBRI_MCP_WRITE": "1" }
}
Only enable the write profile for trusted workspaces/sessions.