# Hotelink MCP server

> Official Hotelink connection guide for AI assistants. Read-only analysis of approved hotel data.

## Connection

- MCP endpoint: https://mcp.hotelink.ai
- Transport: Streamable HTTP
- Authentication: OAuth authorization code with PKCE (S256)
- Authorization server: https://app.hotelink.ai
- OAuth scope: hotelink:read
- Public documentation: https://mcp.hotelink.ai/
- Registry name: io.github.KatyTechnologies/hotelink
- Registry metadata: https://mcp.hotelink.ai/server.json
- Protected resource metadata: https://mcp.hotelink.ai/.well-known/oauth-protected-resource
- Authorization server metadata: https://app.hotelink.ai/.well-known/oauth-authorization-server

## Setup

Add the endpoint as a remote MCP server named Hotelink in an assistant that supports OAuth.
Discover authentication from the endpoint's WWW-Authenticate header and OAuth metadata.
Start the assistant's sign-in flow. The user signs in to their personal Hotelink account,
reviews the account, hotels and connections, and approves access in Hotelink.
Do not ask the user to put passwords or tokens in chat. No Snowflake credentials are needed.
If the assistant cannot add servers itself, guide the user to its connector settings.
Refresh the tools or start a fresh conversation if needed after authorization.

## Tools and verification

Use list_datasets to discover the user's permitted connections and tables.
Use query_sql with connectionId and a read-only SQL statement for exact results and a query ID.
Other tools can vary by connection. Inspect tools/list after sign-in.
Verify access with a small read-only query against a discovered table and show the query ID.
Confirm the expected hotels and available date coverage; never treat missing data as zero.

## Requirements and boundaries

A personal Hotelink account and administrator-granted hotel and connection permissions are required.
Only approved, published data is available. Setup does not import new sources or grant new access.
Queries are read-only and do not edit source records. Results are returned to the chosen assistant.
Automatic token renewal depends on the client's OAuth support. Reconnect when authorization expires.
Revoke an assistant in Hotelink > Access > Connected assistants. Signing out of the website does not revoke it.
For missing data or permissions, contact your organization's Hotelink administrator or onboarding contact.
Never infer successful data access from a connected badge alone.