Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FURIOSA_DASHBOARD_ANON_KEYNoOverride the Supabase anon key. Defaults to the value in config.defaults.json.
FURIOSA_DASHBOARD_SUPABASE_URLNoOverride the Supabase URL. Defaults to the value in config.defaults.json.
FURIOSA_DASHBOARD_REFRESH_TOKENNoSupabase 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 sha filter in list_summaries.

list_summariesA

List compiler benchmark summary rows for a given commit short-sha (first 10 hex chars). Each row's summary field is a JSON blob with detailed compile-time and cycle-count metrics. Optionally filter by test name (exact) or a substring of it, and by cloud/context. Supports pagination.

get_summaryA

Fetch one summaries row by its UUID id, including the full summary JSON metrics blob.

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 recipe param yet. This exists so an AI agent can translate a loose display request ('bridge에 하이라이트 해줘', 'IO 연산은 파란색으로', 'latency 큰 operator 강조해줘') into a small, fixed set of composable view directives instead of re-deriving a full custom rendering from raw IR data on every request. The tool only validates and encodes the recipe as a query param; a deterministic renderer in the dashboard frontend (separate codebase) still needs to be built to read recipe and actually draw it. Until that exists, treat the returned URL's recipe param as inert and the response's recipe field as the artifact to hand to whoever implements that renderer.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hdson-furiosa/furiosa-dashboard-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server