Developers · Guides
The MCP server for developers
Use Bookare from AI tools like Claude Code, or build your own agent on top of it.
Bookare speaks the Model Context Protocol (MCP), the standard way AI assistants use outside tools.
Per-venue server
https://<venue>.bookare.app/mcp: the same operations as the Admin API, as MCP tools (the
reference’s operationId is the tool name).
- Apps (Claude, ChatGPT) connect with OAuth 2.1: dynamic client registration, PKCE (S256), the admin signs in and chooses
read-only or read-and-change. Discovery at
/.well-known/oauth-protected-resourceand/.well-known/oauth-authorization-server. - Developer tools (Claude Code, scripts) use an API key:
Authorization: Bearer bkp_....
claude mcp add --transport http my-studio https://yourvenue.bookare.app/mcp --header "Authorization: Bearer bkp_..."
Transport: Streamable HTTP, stateless (one JSON-RPC message per POST, JSON answers, no session). Methods: initialize, ping,
tools/list, tools/call. Protocol versions 2024-11-05 to 2025-11-25.
Tools depend on the kind of venue; destructive ones are annotated so clients ask for confirmation; read-only connections are refused every change server-side; health data is never exposed.
Platform server
https://bookare.app/mcp, without sign-in: for AI agents that create and set up a venue for a business owner, who then claims
it. See AI agents. Listed in the official MCP Registry as app.bookare/bookare.
Building your own agent
Use either the MCP servers or the REST API: they run the same code. MCP is convenient when your agent framework already speaks it; REST is simpler for fixed workflows.