Connect over MCP

Your company's assistant is also a Model Context Protocol server. Any MCP client can connect to it, so customers can use it from the AI assistants they already have.

The endpoint

https://api.<region>.channelized.ai/v1/<company-key>/mcp

<region> is eu or us, the region your company was set up in.
<company-key> is your company's key. The console's Connect an assistant page shows the full address, ready to copy.

The endpoint speaks JSON-RPC 2.0 over HTTP POST. It does not stream. The full contract is in the API reference.

Guests and signed-in customers

Anyone can connect without signing in. They are a guest, and the public tools work for them: asking the assistant a question, for example.

Some tools act on a customer's own data, such as their account or their orders. Those need the customer to sign in with your company's login, which your team sets up in the console (Connect an assistant):

The client calls a personal tool without a token, and gets 401 with a WWW-Authenticate header.
The header points to the sign-in discovery document at /.well-known/oauth-protected-resource/v1/<company-key>/mcp. It names your company's authorization server, at /v1/<company-key>/oauth.
The client runs the sign-in there (OAuth 2.1 with PKCE). The customer allows the client, then signs in on your company's login page. MCP clients such as ChatGPT and Claude do this for you. See Customer sign-in in the API reference.
The client retries with Authorization: Bearer <token>, and the personal tools now work.

If your company has not set up customer sign-in, everyone is a guest. A personal tool then answers with a message that sign-in is not available instead of 401, the discovery document answers 404, and a request that sends a token is refused with 401 and error="invalid_token".

A guest's tools/list includes the personal tools, so a client that lists once before sign-in still knows them. Every tool's securitySchemes lists both noauth and oauth2, because ChatGPT hides a tool that lists oauth2 alone until the account is linked. A personal tool called as a guest answers 401, and its result carries the same challenge in _meta["mcp/www_authenticate"], which is where ChatGPT looks for it. Without customer sign-in, tools/list leaves the personal tools out.

Sessions

initialize returns an Mcp-Session-Id header. Send it on later requests so the assistant keeps the conversation together. If a request answers 404 with "Session not found", call initialize again.

Limits

One request or a batch of up to 20, at most 256 KB per body.
Requests are rate limited per company and per caller. Over the limit, the endpoint answers 429 with a Retry-After header.

Which tools are there?

Each company offers a different set: the built-in tools of its starting template, minus any the team turned off, plus actions the team added. tools/list always returns the current set. The built-in tools are listed under Built-in tools.

Try it

curl -s https://api.eu.channelized.ai/v1/<company-key>/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'