The server is stateless. It supports the 2026-07-28 protocol revision and falls back to Streamable HTTP for 2025 clients. It doesn’t support the older HTTP+SSE transport, so clients that only offer SSE can’t connect.
Cursor
Add LobbyStack to~/.cursor/mcp.json to use it in every project, or to .cursor/mcp.json in one project:
mcp.json
lobbystack among the MCP servers, and connect it. Cursor opens LobbyStack in your browser: sign in, pick the workspace, uncheck anything Cursor shouldn’t do, and click Allow access.
If the server doesn’t connect, open the Output panel (Cmd+Shift+U) and select MCP Logs.
Cursor with an API key
To use an API key instead, add anAuthorization header. Cursor reads the key from the LOBBYSTACK_API_KEY environment variable:
mcp.json
VS Code
VS Code adds remote servers through a guided flow. Open the Command Palette (Cmd+Shift+P), run MCP: Add Server, choose HTTP (HTTP or Server-Sent Events), and paste the server URL. Enterlobbystack as the server ID, then choose Global > Copilot Global to use LobbyStack in every workspace. VS Code saves this entry in ~/.copilot/mcp-config.json:
~/.copilot/mcp-config.json
.mcp.json file at the root of your workspace.
When VS Code asks you to sign in, LobbyStack opens in your browser. Sign in, pick the workspace, uncheck anything VS Code shouldn’t do, and click Allow access. If the server doesn’t start, run MCP: List Servers, select lobbystack and choose Show Output.
VS Code with an API key
To use an API key instead, add anAuthorization header that reads the key from an environment variable:
~/.copilot/mcp-config.json
LOBBYSTACK_API_KEY in the environment VS Code runs in. In a remote window or a dev container, set it there.
Clients without header support
If a client can only launch local servers, runmcp-remote as the local server and let it add the header. The Claude Desktop guide shows the configuration.