Extend

MCP servers

Lampson is an MCP client. Any server that speaks MCP — over stdio or over HTTP: GitHub, a database, a browser, your own, another Lampson — can be plugged in, and its tools become available to the agent.

Looking for the opposite, letting Claude, Cursor or another agent use your Lampson agents? That's Lampson as an MCP server.

Adding one§

• Terminal: /mcp add github npx -y @modelcontextprotocol/server-github
• Web: MCP in the left panel → + nuevo.
• Ask the agent: "add the GitHub MCP server" — it fills in the config and asks you to confirm.

Or write the file yourself. It is the same format as other tools:

{"mcpServers": {"github": {"command": "npx", "args": ["-y", "@modelcontextprotocol/server-github"],
                           "env": {"GITHUB_TOKEN": "…"}}}}

• ~/lampson/.lampson/mcp.json is global — one config, every project you open.
• <project>/.lampson/mcp.json is per project; a server with the same name overrides the global one.
• "disabled": true keeps an entry without starting it. "cwd" defaults to the project folder.

HTTP servers§

A remote server is connected by its URL, in the same format as Claude Code:

{"mcpServers": {"proveedor": {"url": "https://proveedor.com/w/ventas/v1/mcp",
                              "headers": {"Authorization": "Bearer ${LAMPSON_PROVEEDOR_KEY}"}}}}

${LAMPSON_…} is replaced with the value from ~/lampson/.env, so the key isn't written in mcp.json. Also: /mcp add proveedor https://…/v1/mcp. With this, one Lampson uses another Lampson's agent — agent ↔ agent.

How it behaves§

• Each server starts when Lampson does and is supervised; one that dies shows error in /mcp and the panel.
• Its tools appear to the model as mcp_<server>_<tool>. build and worker see all of them; the read-only profiles only see those the server marks read-only.
• Every call goes through permissions: asks by default, runs in yolo, denied in strict. Every call is in the session trace.

Not yet supported: resources and prompts.