MCP Clients

Any client that speaks the Streamable HTTP MCP transport can connect. All you need is a workspace endpoint:

http://127.0.0.1:18765/mcp/<uuid>

(Copy it from the panel's workspace card.)

Claude Desktop

Edit the MCP configuration (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "workspace": {
      "url": "http://127.0.0.1:18765/mcp/<uuid>"
    }
  }
}

Restart Claude Desktop and the tools appear in the available-tools list.

Cursor

Settings → MCP → Add a new MCP Server:

• Type: Streamable HTTP (or the URL type)
• URL: http://127.0.0.1:18765/mcp/<uuid>

Or in .cursor/mcp.json:

{
  "mcpServers": {
    "workspace": {
      "url": "http://127.0.0.1:18765/mcp/<uuid>"
    }
  }
}

Other clients and custom agents

Connecting takes exactly two things:

1. Transport: HTTP POST to the endpoint, JSON-RPC 2.0 (stateless MCP Streamable HTTP; no session header required);
2. Discovery: call initialize → tools/list — every tool arrives with its name, parameter schema and built-in documentation.

Health check: GET <mcp-port>/healthz.

WARNING

The endpoint is the permission: anyone holding the URL can read, write and execute inside that workspace. Do not share local endpoints with untrusted parties; for public endpoints read the boundaries in Public Access.

Multiple clients

Different clients may share one workspace endpoint or each bind their own workspace (different UUIDs) — for example a chat client with read access to repo A while a coding agent works in repo B, without interference.