Connect an assistant#
Contents
Server address
https://mcp.bitebox.gg/api/mcp
Transport
Streamable HTTP (POST only)
Sign-in
OAuth, on canvas.bitebox.gg
Use this address exactly. Do not use the Canvas address (canvas.bitebox.gg) as the server: hosted assistants cannot reach sign-in through it. You do not need a client ID, a client secret or an API key; Bitebox registers your assistant when it first connects.
The quickest route is the MCP tab on your Canvas home page. It has Add to Claude and Add to Cursor buttons and a setup message to paste into other assistants. Its Setup guide link opens these guides in a new tab.
Your assistant can also find these guides by itself. The server's sign-in details and its first message to the assistant both link to the MCP guides on the public Bitebox site.
Claude#
- Click Add to Claude on the Canvas MCP tab, or add a custom connector in Claude's connector settings.
- Name it
Biteboxand set the URL tohttps://mcp.bitebox.gg/api/mcp. Leave the advanced client ID and secret empty. - Click Connect, sign in to Bitebox, then choose what Claude may do and click Allow.
Claude Code#
claude mcp add --transport http bitebox https://mcp.bitebox.gg/api/mcp
Then run /mcp inside Claude Code, pick bitebox and sign in. Do not add an Authorization header; OAuth handles it.
Codex#
codex mcp add bitebox --url https://mcp.bitebox.gg/api/mcp
Codex opens the Bitebox sign-in in your browser. If it does not, run codex mcp login bitebox. Check each step separately:
codex mcp get biteboxshows the saved, enabled server.Successfully logged inmeans sign-in and consent finished.- A successful
workspace_contextcall in a chat means the tools loaded.
A chat that was already open may not load new tools. Restart Codex and try again.
Cursor#
Click Add to Cursor on the Canvas MCP tab, or add the server to ~/.cursor/mcp.json (or a project's .cursor/mcp.json):
{
"mcpServers": {
"bitebox": { "url": "https://mcp.bitebox.gg/api/mcp" }
}
}
In Cursor's MCP settings, connect bitebox, sign in to Bitebox and allow access.
ChatGPT and other assistants#
Any assistant that supports remote MCP servers with OAuth can connect. Add a custom connector with the server address above, sign in, then allow Bitebox. The Canvas MCP tab has a ready-made setup message to paste into the chat.
See your assistant on the canvas#
The button at the bottom right of the canvas shows what your assistant is doing. Closed eyes mean no assistant is connected. Click it to connect one.
Once one is connected, a moving border means it is changing something, and a number shows how many changes are new to you. Amber with words means it is waiting for your answer, and a red slash means you stopped it.
Hover to read what is happening. Click to stop it, review its changes, or answer it.
To hide the button, click Hide assistant from canvas in its menu, or turn off Show assistant on canvases on the MCP page. If an assistant is connected, the button still appears while it is working or needs you.
Check it works#
Ask your assistant to call workspace_context. It answers with what you allowed and the tool groups the server offers; project_list then lists your projects. If that works, you are connected.
Get new tools after a release#
Bitebox changes its tools when it releases, and when it turns on a feature for your account. Your assistant does not get a message when this happens. It keeps the tool list it read when it connected.
To get the new tools, reconnect the server. In Claude Code, run /mcp, pick bitebox and choose Reconnect. In other assistants, restart the assistant, or disconnect and connect the server again in its settings.
The MCP changelog lists what changed in each release. It also shows the server version these guides come from. Your assistant receives a server version when it connects (serverInfo.version). If the part after the last dot is not the same as on the changelog page, a release changed the tools since your assistant connected, so reconnect. A feature turned on for your account does not change the version, so reconnect after that too.