Connect Botize to other MCP assistants

If your assistant doesn't have its own guide, you can still connect it as long as it meets the requirements.

What your assistant needs

Support for remote MCP servers over HTTP (Streamable HTTP). Clients that only support local servers, installed on your computer, can't connect directly.
Support for OAuth with dynamic client registration. Botize doesn't issue keys or tokens you can copy: access is always authorized from Botize.

Besides Claude, ChatGPT and Claude Code, we know it works with Antigravity.

In your assistant's settings, look for Connectors, Integrations, MCP servers or similar, and add a remote server.
Use this address, exactly:
```
https://webhook.botize.es/mcp
```
If it asks for an authentication type, choose OAuth. If it asks for a Client ID or Client secret, leave them empty: your assistant registers itself.
When you connect, Botize opens: sign in, click Authorize and, if you already have an MCP, choose yours (why it matters) and click Connect.
Check that it works by asking: "List my Botize tasks".

Check the address. It must be https://webhook.botize.es/mcp. The page botize.com/en/mcp explains the MCP, but it isn't the server.
Check that the server is set as remote, not local.
If your assistant asks you to paste a key, it doesn't support OAuth and can't connect to Botize today.

If you've connected an assistant that isn't listed here, or can't manage to, write to us and tell us which one. It helps us expand these guides.

OAuth, discovery and expiry details: How an MCP connection works and auth.md.