io.github.lobbystack/lobbystack
LobbyStack
Is the LobbyStack MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.
AI receptionist: read calls, messages and contacts, book appointments, and update hours and FAQs.
needs auth probed 2026-11-14 · unchanged since 2026-11-13 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":{"code":"unauthorized","message":"Sign in with OAuth, or send a LobbyStack API key as Authorization: - Endpoint
- https://app.lobbystack.com/api/mcp (streamable-http)
- Host
- app.lobbystack.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://app.lobbystack.com/api/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server app.lobbystack.com, PKCE S256, grants authorization_code, refresh_token.
Scopes business:read business:write calls:read contacts:read contacts:write appointments:read appointments:write messages:read knowledge:write businesses:create partner:read partner.businesses:write partner.demos:write partner.packages:write partner.branding:write partner.templates:write partner.team:write partner.billing:read partner.billing:write offline_access.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/lobbystack/lobbystack
- Website
- https://lobbystack.com/features/mcp/
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention lobbystack or appointments or receptionist.
- OpenProfit io.github.lobbystack/openprofit · needs auth
- FALA ai.elav8.fala/fala · needs auth
- ai.smithery/mjucius-cozi_mcp · not found
- Telofy app.telofy/telofy · needs auth
- Nexwin AI au.com.nexwin/nexwin · alive
- Porsche Service Calculator (Garage Kuhn) ch.servicekuhn/service-rechner · alive
- AgentBookable com.agentbookable/mcp · alive
- com.bookingmaven/marketplace · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.