@claxedo/mcp

@claxedo/mcp is a standalone MCP server exposing Claxedo runtime tools — process management, log retrieval and summarization, session messages, and browser control — to any MCP client. It is a local operator tool: run it on the same machine as the Claxedo loopback endpoint, or against an intentionally configured signed remote server. It points at the server via CLAXEDO_SERVER_URL (default http://127.0.0.1:3001).

Its WorkGraph tools are northbound clients of the authenticated WorkGraph HTTP contract. Local Claxedo agent Sessions expose the same schemas through direct in-process tools. Hosted embedded tools remain unavailable until the durable invoking Session supplies verified organization-and-user provenance.

Install

npm install @claxedo/mcp

Or launch the bridge directly for an MCP client config:

npx -y @claxedo/mcp

Configuration

Point the server at a Claxedo endpoint and (optionally) restrict it to read-only tools:

CLAXEDO_SERVER_URL=http://127.0.0.1:3001   # loopback for local use
CLAXEDO_MCP_MODE=read-only                 # or CLAXEDO_MCP_READ_ONLY=1

Supported env: CLAXEDO_SERVER_URL, OPENCODE_API_DIR, CLAXEDO_WORKSPACE_ID, CLAXEDO_AUTH_TOKEN (signed remote only), and the read-only flags.

Tool surface

Trust model

This MCP is a local operator tool — do not expose it as a shared remote endpoint. The process tool mutates .claxedo/processes.jsonc and starts/stops long-running commands; summarize_logs sends log text (possibly containing secrets) to a model; browser tools drive the desktop bridge. Treat remote CLAXEDO_SERVER_URL values as privileged and pair any bearer token with server-side audit logging.

Full API

See the README on GitHub for the full trust model, mode details, per-tool risk notes, and audit expectations.