MCP Setup

Expose Lobby project tools and demo uploads to local MCP clients.

After installing and signing in, configure a local stdio server:

{
  "mcpServers": {
    "coding": {
      "command": "lobby",
      "args": [
        "mcp",
        "--conversation",
        "00000000-0000-4000-8000-000000000001",
        "--repository",
        "123456789"
      ]
    }
  }
}

Use the executable’s absolute path if the client cannot find lobby. The MCP process must run as the same local user that completed lobby login.

With --conversation, the server exposes read-only project, task, and comment tools. --repository enables upload_demo. Inside an eligible Lobby agent, scope is inherited and write tools are also available.

Tool	Purpose
`get_project`	Read the project brief and current task link.
`list_tasks`, `get_task`, `list_comments`, `list_task_statuses`	Read paged project work.
`save_project`, `save_task`, `save_comment`, `link_task`	Mutate project work inside an authorized writable agent.
`upload_demo`	Upload an existing reviewed MP4/WebM and return a private viewer URL.

Tool discovery returns the current schemas, field limits, and read/write hints; use those definitions instead of copying internal HTTP request bodies. A hosted MCP server cannot read local files or reuse the local CLI session, so Lobby does not currently advertise one.