How an MCP connection works

When you connect an AI assistant to Botize, you don't simply hand over your whole account: you connect it to an MCP, a set of tools that belongs to you. Understanding that difference avoids the most common problem, which is ending up connected to an empty MCP.

What an MCP is

This is the definition you'll see in Botize when connecting:

An MCP is a set of Botize tools that belongs to you. You can connect it to this client and to any other, and it keeps its tools when you connect again.

In other words:

The MCP is yours, not the assistant's. If you connect Claude and ChatGPT to the same MCP, both have the same tools.
It has a name, the one you give it (for example, "Telegram channels"), so you can tell several apart.
It keeps the tools you approve. If you disconnect and connect again to the same MCP, they're still there.

You'll find them in your account under MCP connections.

What happens when you connect

Your assistant takes you to Botize, where you'll see these screens, in this order:

Sign in to Botize. "Your assistant wants to connect to your account". If you were already signed in, this screen is skipped.
Authorize access. "Your assistant wants to access your Botize account", with the account and the permission requested. Click Authorize, or Deny if you don't recognize it.
Which MCP do you want to connect? Your MCPs are listed with their number of tools, plus Create a new MCP, where you give it a name. Choose and click Connect. The first time you connect there's nothing to choose: Botize creates your first MCP and this screen doesn't appear.

Then you're back in your assistant, connected.

If Botize can't check which MCPs you have, it doesn't create a new one just in case: it shows "We could not complete the connection" and gives no access, so you can try again. What to do

When you connect again, choose the MCP you already have

This is the most important part of this page.

Every time you go through Which MCP do you want to connect? again —because access expired, because you removed the connector, or because you're adding it to another assistant— pick your MCP from the list.

If you click Create a new MCP, you get an empty one, without any of the tools you had approved. Everything seems to work —the connection exists and has permission— but your assistant can no longer do what it used to. Only create a new one when you deliberately want a different set of tools.

No keys to copy

The connection uses OAuth: your assistant registers itself with Botize and gets access when you authorize it. You never copy or paste a key, and if an assistant asks you for a Botize token or API key, that isn't how this MCP connects.

How long access lasts

The access your assistant gets lasts 90 days.
It doesn't renew on its own. When it expires, your assistant will ask you to go through Botize again: sign in, authorize and choose your MCP.
There's no warning beforehand: you'll notice because your assistant asks for permission again. If you choose the same MCP, you lose nothing.

If your assistant doesn't ask and just says the connection is failing, see Your assistant asks for permission again.

One MCP or several

One MCP for all your assistants: the simplest option. What you approve in one, they all have.
One MCP per purpose: for example, one just for posting to your channels, with very few tools, and a full one for managing tasks.

There is currently no limit on MCPs per account or on assistants connected to the same MCP.

Member accounts

If you connect an assistant from a member account, the MCP, its tools and its approvals belong to that account; the operations it uses are charged to the main account's plan.

For developers

Address: https://webhook.botize.es/mcp, Streamable HTTP transport.
Authorization: OAuth 2.0 authorization code flow, PKCE (S256) required and Dynamic Client Registration (RFC 7591). Public client, no secret. Scope AGENT_FULL.
Discovery: https://webhook.botize.es/.well-known/oauth-protected-resource and https://botize.com/.well-known/oauth-authorization-server.
The token lasts 90 days and there is no refresh token: when it expires, the server answers 401 with WWW-Authenticate: Bearer error="invalid_token" and the client must authorize again.
Full walkthrough: auth.md.