MCP Setup

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

The prepared npm package is @abloatai/lobby. Browser login is implemented; server deployment and npm publication are pending. Use the packed artifact against a server with the approval page and local-project endpoint installed. See the implementation and release status.

After installing the artifact and signing in, register the installed server with lobby connect claude or lobby connect codex. Then select your project:

lobby project select opens an interactive picker; use an ID in scripts.

lobby connect claude
cd /path/to/checkout
lobby project select
lobby doctor

Restart the agent after registration. Connect uses the client’s own configuration writer and leaves conflicting registrations unchanged. No model credentials are forwarded. The stdio process runs as the local user who completed lobby login. The project binding is private to this machine and checkout, including its subdirectories. Use lobby project unselect to remove it.

doctor verifies an actual MCP handshake and reports separate authenticated catalog and selected-project checks with recovery guidance. It also reads Claude and Codex registrations, reporting missing, stale or unreadable configuration without changing it. These checks do not prove a running agent has loaded Lobby.

Tools	Local selected checkout
`get_model_connections`, `get_team`, `get_account`	Read existing member connection, team and account metadata; no secrets.
`get_workspace_status`	Available with legacy conversation scope; reads persisted compute state without waking it.
`list_projects`, `get_project`	Read accessible projects and the selected brief.
`list_tasks`, `get_task`, `list_comments`, `list_task_statuses`	Read paged project work.
`save_project`, `save_task`, `save_comment`	Update the selected brief, tasks and comments with member permissions and revision checks.
`upload_demo`	Upload a reviewed recording using an explicit repository ID.

Local agents cannot move cloud conversations, publish repository claims, link conversations, or delete projects. Server access is rechecked for every request. A changed account or user requires selecting the project again.

Existing manual lobby mcp --conversation ID --repository ID configurations remain supported with read-only project operations. In writable Lobby cloud sessions, scope is inherited and the cloud tools remain available. Tool discovery returns current schemas and field limits. Lobby does not advertise a hosted MCP server.

Existing Cursor/manual stdio configurations remain supported. See Cursor MCP. Check lobby auth status for the CLI identity and use lobby accounts switch ACCOUNT_ID to change its account before selecting a project.