MCP configuration
MCP configuration
This guide explains how to connect your AI tool to Fusebase Dashboards using the Model Context Protocol (MCP). Once connected, your tool can access dashboard data according to your token's scopes and permissions.
URL
https://dashboards-mcp.thefusebase.com/mcp
Auth
Authorization: Bearer <token>
Fusebase MCP uses token-in-header authentication only. OAuth is not supported. You must use a Dashboard API token in the Authorization: Bearer '<token>' header.
- In Fusebase Studio, open Organization → Settings → Dashboard API tokens.
- Create a token (name, permissions, scopes). Copy and store the token value securely — it is shown only once.
- Click Configure MCP on any token row (or after creating a token). The modal shows ready-to-use JSON, Copy, and Download options for Claude Code, Cursor, and VS Code.
All clients use the same MCP server URL and auth. Replace '<YOUR_TOKEN>' with your Dashboard API token.
mcp.json (generic)
{
"mcpServers": {
"fusebase-dashboards": {
"type": "http",
"url": "https://dashboards-mcp.thefusebase.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Open Cursor Settings → MCP → Add new global MCP server (or edit the config file). Add the server with type "http", URL, and headers. Replace '<YOUR_TOKEN>' with your token. Save and restart Cursor if needed. For project-level config, create .cursor/mcp.json in the project root; do not commit the token.
.cursor/mcp.json
{
"mcpServers": {
"fusebase-dashboards": {
"type": "http",
"url": "https://dashboards-mcp.thefusebase.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Add the MCP server with HTTP transport and Authorization header in your config (e.g. .mcp.json). User scope: config in your user directory. Project scope: .mcp.json in the project root; each developer uses their own token locally.
.mcp.json
{
"mcpServers": {
"fusebase-dashboards": {
"type": "http",
"url": "https://dashboards-mcp.thefusebase.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Create or edit .vscode/mcp.json. Use the "servers" (or "mcpServers") format with type "http", url, and headers. Replace '<YOUR_TOKEN>' with your token. Run MCP: List Servers from the Command Palette to confirm.
.vscode/mcp.json
{
"servers": {
"fusebase-dashboards": {
"type": "http",
"url": "https://dashboards-mcp.thefusebase.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}- Run and select Other (Antigravity, WebStorm, Claude Desktop, etc.) — mcp_example.json in the CLI.
Choose the “Other (Antigravity…) — mcp_example.json” option in the CLI. - Open in your project — it contains and .
Open .env and copy DASHBOARDS_MCP_URL and DASHBOARDS_MCP_TOKEN (never commit the token). - In Antigravity chat, click the three dots (top-right) → MCP Servers.
Open the chat menu (three dots) and select MCP Servers. - Click Manage MCP Servers.
Click “Manage MCP Servers” in the top-right corner. - Click View raw config, paste the server config (Antigravity uses for remote MCP servers).
Click View raw config to open the JSON config editor. - Paste the server config into the editor and replace the token with (keep as the MCP URL). Then click Refresh in Manage MCP Servers, or restart Antigravity.
Paste the config and set Authorization: Bearer <token> (never paste/commit real tokens into repos). mcp_config.json (Antigravity)
{ "mcpServers": { "fusebase-dashboards": { "serverUrl": "https://dashboards-mcp.thefusebase.com/mcp", "headers": { "Authorization": "Bearer <YOUR_TOKEN>" } } } } - Return to Manage MCP Servers and click Refresh. When the server loads, you should see and the list of available tools.
Click Refresh to reload MCP servers. 
Once loaded, the server appears and tools become available. - OptionalIn the chat, send a quick verification message and confirm the agent can call for .
Ask the agent whether it can see the Fusebase Dashboards MCP server. 
If configured correctly, you’ll see a tools_list call and the tool names.
User-level: config in your editor's global directory; token stays on your machine. Project-level: config in the repo (e.g. .cursor/mcp.json); share the shape with the team but do not commit the token.
If your tool supports MCP over HTTP and custom headers, use the same URL and Authorization: Bearer '<YOUR_TOKEN>' header. If it only supports stdio, use an MCP bridge (e.g. mcp-remote) that forwards the header.
mcp.json (generic)
{
"mcpServers": {
"fusebase-dashboards": {
"type": "http",
"url": "https://dashboards-mcp.thefusebase.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}- Authentication: Authentication errors: ensure the header is exactly Authorization: Bearer '<token>'; confirm the token is a Dashboard API token from Settings → Dashboard API tokens; if revoked, create a new one.
- Server not loading: Server not loading: check the URL (no trailing slash); ensure your client supports HTTP MCP and custom headers; try restarting the editor.
- Token in version control: Never commit the real token; use '<YOUR_TOKEN>' or an env placeholder in committed configs.
- Does Fusebase MCP support OAuth? Fusebase Dashboards MCP uses Bearer token in the header only. Create a token in Organization → Settings → Dashboard API tokens and put it in the Authorization header.
- Where do I get the exact JSON for my editor? In Fusebase Studio go to Settings → Dashboard API tokens, then click Configure MCP on a token. The modal shows the JSON, Copy, and Download options for your editor.
- Can I use Fusebase MCP without a human in the loop? Yes. Because auth is a static Bearer token, you can use it in scripts, CI, or headless agents. Create a token, put it in the MCP config, and ensure the token's scopes match what the automation needs.