Developer docs

Connect your assistant

Add the BookDinePlay MCP server to Claude, Claude Code, VS Code or ChatGPT with one URL, sign in with your BookDinePlay account, and check that it works.

Every client needs the same two things: the server URL and a sign-in with your BookDinePlay account.

https://mcp.bookdineplay.com

The server uses the Streamable HTTP transport and OAuth. The first time you connect, your client opens a BookDinePlay sign-in page in the browser; after you sign in the assistant can use the tools. There is no API key to copy and nothing to install.

Claude

In Claude (claude.ai or the desktop app) open Settings → Connectors → Add custom connector, name it BookDinePlay and paste the URL above. Then choose Connect and sign in. In a new conversation, enable the connector from the tools menu and ask, for example, "Who am I on BookDinePlay?".

Claude Code, VS Code

For Claude Code, add the server with one command:

claude mcp add --transport http bookdineplay https://mcp.bookdineplay.com

Then start claude, run /mcp, pick bookdineplay and choose to authenticate. For VS Code, save this as .vscode/mcp.json in your workspace:

{
  "servers": {
    "bookdineplay": {
      "type": "http",
      "url": "https://mcp.bookdineplay.com"
    }
  }
}

Then run MCP: List Servers from the command palette, start bookdineplay and sign in when asked.

ChatGPT

In ChatGPT open Settings → Connectors, enable developer mode if your plan or workspace requires it, create a connector, paste the URL above and choose OAuth as the authentication. Which plans and workspaces may add a custom connector is decided by OpenAI and can change, so check ChatGPT's own help if the option is missing.

Check that it works

Ask the assistant "Who am I on BookDinePlay?". It calls the whoami tool and answers with your role, your venue, your plan and whether the terms still need accepting. A person without a venue yet is told so and can go on to the guided sign-up described under Tools. To see what a guest gets, ask it to find a venue in a city.

Good to know

  • Your permissions are the console's. If the console refuses something for your plan or role, so does the assistant, with the same message.
  • Two scopes. A client asks for bookdineplay:read to use read-only tools and bookdineplay:write for tools that change data. You can grant read only.
  • Revoking access. Remove the connector in your client. Signing in again is always needed after that.
  • No dynamic registration. Clients that identify themselves with a published client metadata document, or that are pre-registered with BookDinePlay, can connect. A client that can only register itself on the fly is refused.