Connect an AI tool to Chatterbox through its MCP server at https://chatterbox.cbrspn.cloud/api/v1/mcp/. The endpoint accepts JSON-RPC 2.0 requests over HTTP POST and uses a bearer token. Keep that token private, add the endpoint and authorization header to your MCP client, then test the connection before using it with business information.
An MCP connection is separate from the chat bubble on your website. The widget answers visitors from your business content and asks for contact details when that material runs out. The MCP server is the route for connecting your own compatible AI tool to Chatterbox.
That distinction is worth making before setup. Adding an MCP server to a desktop tool does not install the customer-facing widget. Installing the widget does not automatically give another AI tool access. They are two different connections for two different jobs.
What do you need before connecting an AI tool with MCP?
You need an MCP-compatible client, the Chatterbox server address, and a bearer token for authorization. The server address is:
https://chatterbox.cbrspn.cloud/api/v1/mcp/
Keep the trailing slash. Chatterbox accepts MCP requests at that address through HTTP POST. The messages use JSON-RPC 2.0, and authorization travels in a bearer header.
Treat the bearer token like a password. Do not put it in a website script, commit it to a repository, paste it into a shared support ticket, or include it in a screenshot. The script tag used by the public widget and the bearer token used by an MCP client are not interchangeable.
Decide which account the connection should reach before you create the client entry. If you manage several businesses, a convenient connection is not a reason to blur ownership. Each Chatterbox client's knowledge base is isolated from every other client's. Keep your local MCP configuration just as deliberate.
What goes into the MCP client configuration?
MCP clients use different settings screens and configuration file shapes. Whatever form your client expects, it needs these two connection details:
Server URL: https://chatterbox.cbrspn.cloud/api/v1/mcp/
Authorization: Bearer <your-token>
Some clients ask for a remote server URL and headers. Others expect a JSON object. Follow the client's documentation for the wrapper, but copy the Chatterbox URL exactly and place the token in the authorization header rather than in the URL.
Save the entry under a plain name such as chatterbox. If the client needs to restart before it discovers a new server, restart it. Then use the client's own server or tools view to confirm that the connection was discovered. This check separates a configuration problem from a later request problem.
How do you test the website chatbot MCP connection safely?
Begin with a read-only check offered by your client rather than changing business material immediately. Confirm that the client can reach the server and that the account shown is the one you intended to connect.
If the connection fails, inspect the small things first. Confirm that the request is going to the HTTPS address above, uses POST, retains the trailing slash, and carries Authorization: Bearer followed by the token. A missing space after Bearer, a copied quote mark, or a token placed in the URL can make a correct server look unavailable.
Do not solve an authorization error by pasting the token into more places. Remove any exposed copy, replace the credential through the account process, and update the one private configuration that needs it.
Where does MCP stop and the website widget begin?
MCP gives a compatible AI tool a way to connect to Chatterbox. The website widget still serves the visitor. Chatterbox answers that visitor from the business's own material, shows the source passage behind an answer, and says it cannot find the answer when the material does not settle the question. It then asks for a name, phone number, and email so a person can follow up.
This boundary keeps the setup honest. An MCP client is not a live-agent handoff, a phone bot, or a replacement for the website widget. It is an authenticated route for your own tool. The public conversation remains on the business website, and the missing answer still belongs with a person.
Once the connection works, start with one account and one deliberate task. Check the result against the Chatterbox dashboard before expanding how you use it. A short test with the right business is safer than a broad connection whose account and limits nobody verified.