Connecting an AI agent

Bao exposes an MCP (Model Context Protocol) server over Streamable HTTP transport. Any compatible agent plugs into it and drives your Discord servers in plain language.

The server is hosted by Bao. There is nothing to install and nothing to update: new tools appear on their own.

Creating a link

In the dashboard, Configuration → MCP. Give the link a name (the agent's, or the machine's), and Bao hands you a connection URL:

https://<bao-url>/mcp/bao_mcp_...

The secret is shown only once, at creation. It is never kept in the clear: only its fingerprint is stored. Lost, it is regenerated.

Pasting it into an agent

Most connector interfaces ask only for a name and a URL: paste the link as it is.

On Claude: Settings → Connectors → Add custom connector.

The token is also accepted as a header, for clients that allow it:

claude mcp add --transport http bao https://<bao-url>/mcp \
  --header "Authorization: Bearer bao_mcp_..."

One token, one user

A token belongs to a person, not to a server. It opens access to every Discord server that person administers and where Bao is installed. Each tool takes a serveur parameter.

The list is recalculated on every call, never frozen into the token:

• adding Bao to a new server makes it drivable immediately;
• losing administration rights cuts access on the spot.

Revoking

One click on revoke and the link is worthless. Create as many links as you have agents: you will be able to cut them separately.

The agent calls from its own servers

An important point: your agent calls Bao from its own servers, not from your machine.

• Your computer can stay switched off. You can drive everything from a phone.
• The URL must be public and over https. A local address is refused by web and mobile agents.

The MCP connector is reserved for Bao Royal.