# Configure MCP

> Connect a compatible assistant to the directory or one specific business.

Canonical: https://bookwise.live/docs/mcp-setup

MCP server version: 1.1.0

## Choose your endpoint

Bookwise uses MCP over Streamable HTTP. In a client that supports remote MCP, choose an HTTP/remote server connection and enter one of these URLs. Field names and configuration-file locations vary by client; these values are transport settings, not a universal client config file.

### Directory — discover and book across businesses

```text
https://bookwise.live/api/mcp
```

### Business (deprecated alias)

```text
https://bookwise.live/api/b/your-business-slug/mcp
```

| Endpoint | Available tools | Business selection |
| --- | --- | --- |
| Directory | 27 tools | Pass a business ID or booking-page slug as businessId |
| Business (deprecated) | 25 tools | Scoped to that business; use the directory endpoint with its slug instead |

## Connection settings

| Setting | Value |
| --- | --- |
| Transport | Streamable HTTP |
| URL | Directory or business URL above |
| Public discovery | No account required |
| Booking management | holdToken or accessToken in tool arguments, as described by the tool |
| Owner operations | Valid owner session bearer token or existing signed session cookie |

Use an HTTPS deployment URL for a remote client. A localhost address is reachable only by a client running in an environment that can access that machine. Client support and organization policies determine whether remote MCP connections and custom headers are available.

## Owner access is separate

### Owner session header

```http
Authorization: Bearer <valid-owner-session-token>
```

The server validates existing owner sessions and business ownership on every owner call. A user ID, business ID or customer booking token is not an owner credential. Expired or revoked sessions stop working. Do not put session tokens in public URLs, repositories, browser-delivered examples or prompts.

> **Authentication support**: This server does not provide a separate MCP OAuth onboarding flow. Clients that require OAuth-only protected MCP servers cannot use owner tools through that flow. Use a trusted integration that can send the existing owner session credentials.

## Check the connection

1. Connect with an MCP client and let it negotiate the protocol.
2. Call tools/list and inspect each inputSchema, description and outputSchema.
3. On the directory, call search_businesses with a relevant query. On a business endpoint, call get_business with no arguments.
4. Use real returned business/offering IDs for the next request. Read get_business.bookingParamsSchema before constructing params.

A business URL returning 404 usually means the slug is wrong or the business is not published. Tool errors are different from connection errors; see [Errors and retries](https://bookwise.live/docs/errors).