MCP Endpoint
Connect MCP servers on your own computer or private network through a connector that dials out.
MCP Endpoint lets an assistant use tools that run on your computer or private network without a public URL or an open port. A connector running next to your MCP servers opens a WebSocket connection out to Assistant Core, and the assistant calls tools over that connection in chat, voice, and device sessions.
The connector can be mcp_pipe.py, xiaozhi-client, or any client that supports the Xiaozhi MCP Endpoint. Devices and tools already used with Xiaozhi can move to Assistant Core unchanged.
MCP Server Or MCP Endpoint?
Both live on the MCP page of the Admin Panel.
| Remote servers tab (MCP Server) | Local connector tab (MCP Endpoint) |
|---|---|
| Assistant Core calls your Server URL | Your connector connects to Assistant Core |
| The MCP server needs a URL reachable from the internet | The MCP server can sit behind NAT or a firewall, or run locally over stdio |
| Authenticated with OAuth, Bearer, API key… | Authenticated with a secret Connector URL |
If your MCP server already has a public URL, use MCP Server.
Connect A Connector
-
Open the Admin Panel and select the assistant.
-
Go to MCP → Local connector.
-
Turn on MCP Endpoint.
-
Click Create Connector URL and copy it right away. The URL is shown only once.
-
Configure your connector with that URL, for example:
export MCP_ENDPOINT="wss://api.assistantcore.com/mcp_endpoint/mcp/?token=mcpe_..." python mcp_pipe.py server.py -
Back in the Admin Panel, click Refresh Tools to see the tool list. Turn off tools the assistant does not need.
If the UI says the MCP Endpoint is unavailable, a system admin must configure the backend first.
Keep The Connector URL Secret
The Connector URL is a credential. Anyone with it can register tools for the assistant and receive its tool calls and their arguments.
- Do not commit the URL to git or paste it anywhere public.
- If the URL leaks or is lost, click Regenerate URL. The old URL stops working immediately and connectors using it are disconnected.
- Click Revoke URL to disconnect every connector.
If the connector exposes tools that run shell commands or touch files, the assistant can act on that machine on behalf of whoever chats with it. Enable it only for assistants whose users you trust, run the connector under a low-privilege account, and turn off tools you do not need.
No Tools Showing?
- Check that MCP Endpoint is on and a Connector URL exists.
- Check that the connector is running with the latest URL. Old URLs are rejected after you regenerate.
- Check the connector logs to confirm your MCP servers started.
- Check your account's role and permissions in the assistant.