This article shows you how to let an AI assistant work inside your HueChat account through the Model Context Protocol (MCP). With MCP, a tool such as Claude, Codex or n8n can look up Contacts, read conversations or send messages on your behalf, limited to the scopes you approve.
Screenshot: The HueChat MCP card in Settings with the request note field and the Request key button.
The card also shows the MCP endpoint, the exact Authorization: Bearer header to send, and the list of included tools your key may use.
Most MCP clients accept a configuration like this:
{
"mcpServers": {
"huechat": {
"type": "http",
"url": "<the MCP endpoint shown in the card>",
"headers": {
"Authorization": "Bearer <your MCP key>",
"MCP-Protocol-Version": "2025-11-25"
}
}
}
}
The server speaks streamable HTTP. Send Content-Type: application/json and Accept: application/json, text/event-stream on every request. The handshake (initialize, notifications/initialized, tools/list, tools/call) and a worked example are in the Developer Hub at https://developers.huechat.ai.
The tool list is filtered by the key's scopes. The key carries mcp:use plus only the resource scopes the enabled tools need, for example contacts:read to search Contacts or messages:write to send a message. Read-only tools are the safest place to start.
Write tools create or change real customer data. Before you connect an assistant, review the included tools on the card and ask for the smallest scope set that does the job.
The key stops working immediately. Request a new key if you need access again. Access also ends when the key expires or when the requesting administrator loses administrator rights.
A 401 usually means the Bearer prefix is missing or you are using a REST key instead of the MCP key. An empty tool list means the key has no scopes for the tools you expected; ask support@huechat.ai to adjust them.