MCP overview

BitBoard implements the Model Context Protocol so external agents can create, inspect, run, and share dashboards.

https://app.bitboard.work/mcp

Connect an MCP-compatible client and authorize it with your BitBoard account. See Connect your agent for client-specific steps.

MCP agents and Ask are different

Claude, Cursor, ChatGPT, Codex, and other MCP clients are third-party agents. They call BitBoard’s MCP tools to work on dashboards.

Ask is a separate, built-in BitBoard agent. Connecting an external agent does not power or replace Ask.

Dashboard tools

Dashboard tools have stable names such as dashboard_create, dashboard_get, and dashboard_update. They cover:

• dashboard discovery and lifecycle;
• loading and inspecting data;
• creating and updating blocks;
• running blocks;
• layout and visibility; and
• discovering dashboard connections.

See the Dashboard MCP tools reference for inputs and behavior.

Dynamic connection tools

Connected apps and repositories can add tools to MCP discovery for the authenticated user. Their availability depends on the connections in that BitBoard account.

Agents should discover these tools at runtime instead of hard-coding their names. Use a list operation to find a tool, then a describe operation to retrieve its detailed parameters when needed.

MCP discovery can also include supporting BitBoard tools outside the dashboard reference. Treat the client’s discovered tool list as the source of truth for the current session.

Authorization

BitBoard uses OAuth 2.0 authorization for remote MCP clients. The authenticated BitBoard user determines which dashboards, connections, and repository tools the client can discover and call.