Skip to main content
HueChat exposes an account-scoped MCP server over streamable HTTP:

Getting a key

MCP uses its own, separately approved credential. As an account administrator, open Settings → Integrations → MCP, request access for the account, wait for approval, then copy the key when it is revealed. It is shown once.
A REST scoped key cannot be used for MCP, and an MCP key is rejected on the REST routes. The MCP key must carry mcp:use plus only the resource scopes the tools you enable actually need.
The requester must remain an active administrator; demotion, removal, key revocation or expiry disables the credential.

Required headers

Handshake

1

Initialize

2

Send the initialized notification

3

List the tools your key may use

The list is filtered by the key’s scopes.
4

Call a read-only tool

Client configuration

Most MCP clients accept this shape:
Write tools create or change customer data. Grant the smallest scope set and review what an assistant is allowed to do before connecting it.