furiosa-dashboard-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FURIOSA_DASHBOARD_ANON_KEY | No | Override the Supabase anon key. Defaults to the value in config.defaults.json. | |
| FURIOSA_DASHBOARD_SUPABASE_URL | No | Override the Supabase URL. Defaults to the value in config.defaults.json. | |
| FURIOSA_DASHBOARD_REFRESH_TOKEN | No | Supabase refresh token, needed instead of a session file (e.g., on a new machine without ~/.config/furiosa-dashboard-mcp/session.json). Obtain manually via browser dev tools as described in the README. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_recent_commitsA | List the most recently benchmarked commits from master_commits, newest first. Note: the full sha returned here must be truncated to its first 10 hex characters before using it as the |
| list_summariesA | List compiler benchmark summary rows for a given commit short-sha (first 10 hex chars). Each row's |
| get_summaryA | Fetch one summaries row by its UUID id, including the full |
| get_ir_viewer_urlA | Build a dashboard.furiosa.dev/ir-text-viewer link for a given commit + context + test, so it can be opened directly in a browser instead of running anything locally. Resolves the short-sha to the full commit sha required by the viewer URL via master_commits. |
| build_ir_view_recipe_urlA | DRAFT / PROPOSED contract only -- dashboard.furiosa.dev does not read this |
| get_ir_viewer_compare_urlB | Build a compare link on ir-viewer.furiosa.dev (a separate viewer from dashboard.furiosa.dev's ir-text-viewer) for a base vs current commit. Accepts short-shas directly, no full-sha lookup needed. |
| get_tactic_debug_urlA | Build a tactic-debug compare link for a base vs current commit. Accepts short-shas directly. |
| get_tc_viewer_urlA | Build a tc-viewer compare link for a base vs current commit. Unlike the other two compare viewers, tc-viewer takes a single (not comma-paired) context/test and separate sha/baseSha params. |
| compare_commitsA | Diff all matching benchmark rows (matched by test+context+cloud) between a base and current commit short-sha. Reports added/removed tests, pass/fail status changes, the top N regressions/improvements for both execution-style tests (status + average_actual_cycle) and compile-style tests (rlir total_cycle + total compile_time), plus a generic fieldChanges section that flattens and ranks every numeric field found anywhere in the summary JSON blob (memory, tactic costs, dram usage, per-phase cpu time, etc.) -- use fieldChanges as a first-pass scan for what's worth attention before drilling into a specific metric. Optionally scope the comparison with test/testContains/context/cloud filters, same as list_summaries. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
The data-retrieval tools are distinct, but the five URL-builder tools blur together: get_ir_viewer_url vs get_ir_viewer_compare_url and get_tc_viewer_url vs get_tactic_debug_url are easy to confuse. The descriptions help clarify the differences, but an agent could still pick the wrong viewer builder without careful reading.
Tool names are mostly consistent snake_case verb_noun forms (list_*, get_*, compare_*), which is predictable. Minor deviations exist in the URL-builder cluster, especially build_ir_view_recipe_url using 'build' instead of 'get' and the inconsistent 'tc' abbreviation vs full 'tactic'.
Nine tools is a reasonable, well-scoped count for a benchmark dashboard MCP. However, build_ir_view_recipe_url is explicitly a draft/proposed contract with no working renderer, so one tool is currently more speculative than functional.
The core read-only workflow is covered: listing benchmarked commits, querying summaries, fetching full summary details, comparing commits, and generating viewer URLs. Minor gaps include no way to enumerate available contexts/clouds/tests directly and no get-commit-by-sha tool, but agents can work around these from the existing list tools.