Guides

Connecting MCP tools

codel00p speaks the Model Context Protocol in both directions: it can use external MCP tools, and it can serve its own memory and sessions to other clients.

Attach an external server

Pass --mcp-server as name=command to launch a stdio MCP server for a run. Its tools appear to the model as mcp.<name>.<tool> and run under the same permission checks as native tools.

codel00p ...scope agent run "List the open issues" \
  --mcp-server github=mcp-server-github \
  --tool-set all

A workspace can also declare servers in .codel00p/mcp.json so they load automatically.

Inspect connectors

Check which tools a server exposes without making a model call, and run redacted diagnostics if a connection misbehaves.

codel00p ...scope agent mcp list
codel00p ...scope agent mcp doctor

Serve codel00p to other clients

Run codel00p as a stdio MCP server. It exposes project memory search, list, and show, reviewed candidate creation and review, and read-only session replay, plus JSON resources at codel00p://memory/{id} and codel00p://sessions/{id}.

codel00p ...scope mcp serve

Remembered ask-mode connector decisions can be reviewed with mcp permissions.