mcp-wandb
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WANDB_API_KEY | Yes | Your Weights & Biases API key for authentication. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_wandb_projectsB | Get a list of projects from Weights & Biases. |
| list_wandb_runsB | List all runs for a given W&B project. |
| list_project_metricsA | List all unique metric names logged in a W&B project. |
| plot_run_metricB | Plot the requested metrics and return the base-64-encoded PNG. |
| get_run_detailsB | Retrieve detailed information about a W&B run, including:
|
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 5 tools
Each tool targets a distinct resource-action pair: projects, runs, run details, metric names, and plot output. There is no meaningful overlap or risk of confusion.
All names are lowercase snake_case and verb-first, but conventions are mixed: 'get' and 'list' are used inconsistently for collection-returning tools, and the 'wandb' prefix appears on only some tools. Still readable and predictable enough for an agent.
Five tools form a compact, well-scoped set for reading and visualizing W&B data. Each tool serves a clear purpose without redundancy.
Covers project discovery, run listing, run details, metric discovery, and plotting. However, raw metric history is only accessible through an image plot, and there is no run comparison or filtering, which are common W&B workflows.