The Model Context Protocol endpoint. An MCP-compatible AI assistant connects to https://app.hosttools.com/mcp and gets the same account data as the REST API above (listings, reservations, the calendar, messages, analytics) as tools it can call during a conversation.

Note: this is not a REST endpoint you call by hand. The body is JSON-RPC 2.0 and the conversation is driven by your MCP client. Point the client at the URL and let it handle the protocol; the "Try It" panel will not produce anything useful.

Authorization

Bearer tokens only. The legacy authToken header is not accepted here. Clients discover the OAuth endpoints from the URL itself (see Protected Resource Metadata above), register dynamically via /oauth/register, and run the authorization code flow with PKCE. The scopes granted at authorization decide which tools succeed: every tool stays visible regardless, and one outside the granted scopes returns an insufficient_scope error when called.

Rate limit

300 requests per minute, keyed on the access token (falling back to the client IP for unauthenticated probes). Exceeding it returns 429 with a JSON-RPC error.

Other methods on this path

A GET currently answers 405: the server sends nothing on its own initiative today, so there is no stream for a client to attach to, and compliant clients fall back to request/response. DELETE answers 204.

Setting it up

For connection instructions and the full catalog of tools, resources, and scopes, see How do I use the Host Tools MCP server?.