Weights & Biases MCP
Updated June 2026The Weights & Biases MCP, built by community, provides track ML experiments, compare runs, log metrics and artifacts, manage model registry, and visualize training curves using Weights & Biases — the leading experiment tracking platform for ML teams. It is community-built and best for ai-ml.
by community
About
Track ML experiments, compare runs, log metrics and artifacts, manage model registry, and visualize training curves using Weights & Biases — the leading experiment tracking platform for ML teams.
Trust verdict
How grades are computed →No repository for this entry resolves against the live GitHub API, so there is nothing to verify. It is deliberately left unscored rather than given a number we cannot stand behind.
What could not be measured
These contributed nothing to the score — not a penalty, not a zero. They are why the confidence reads the way it does.
- Source verificationunknown
No repository for this entry resolves against the live GitHub API. Without a confirmed source there is nothing to inspect, so this entry is excluded from trust scoring entirely rather than scored on catalog metadata alone.
What we could verify
No public repository, published package, or project website has been confirmed for Weights & Biases MCP. The description above reflects what the server is reported to do; we have not been able to verify an implementation behind it, so there is no install command to give you and no star count worth quoting.
If you maintain it, or you know the repository, the fastest way to fix this listing is to point us at the source.
Categories
Works With
Frequently Asked Questions
What is Weights & Biases MCP?
Who built Weights & Biases MCP?
Is Weights & Biases MCP free?
How do I install Weights & Biases MCP?
What does Weights & Biases MCP integrate with?
Repo Health
Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.
- Install
- npm
Repo recency not yet available for this server.
Quick Info
- Install Type
- npm
- Author
- community
- Categories
- 2
- Integrations
- 3
Related Servers
DeepSeek MCP
Integrate DeepSeek API for cost-effective reasoning and code generation — access DeepSeek-V3 and DeepSeek-R1 models for complex problem solving, mathematical reasoning, and code synthesis.
Qwen (Alibaba Cloud) MCP
Access Alibaba Cloud Qwen LLM family via API — long-context processing with Qwen-Long, multimodal with Qwen-VL, and code generation with Qwen-Coder for multilingual AI workflows.
Moonshot AI (Kimi) MCP
Connect to Moonshot AI Kimi API for long-context document analysis up to 200K tokens, Chinese-English bilingual processing, web search-augmented generation, and multimodal understanding.
MCP Jenkins
a Python MCP server for Jenkins (lanbaoshen/mcp-jenkins, published to PyPI as mcp-jenkins) and the alternative to the official Jenkins MCP plugin: where the plugin has to be installed into the controller from the update centre, this one runs beside Jenkins and talks to it over the ordinary REST API, so you can point it at a Jenkins you do not administer. Install it with uvx mcp-jenkins, pip install mcp-jenkins, or the ghcr.io/lanbaoshen/mcp-jenkins container. Credentials go in as --jenkins-url, --jenkins-username and --jenkins-password (an API token works in place of the password), and on the HTTP transport the same three can be supplied per-connection as the x-jenkins-url, x-jenkins-username and x-jenkins-password headers, which is what lets one running instance serve several Jenkins controllers. Three transports are available via --transport: stdio (the default), sse, and streamable-http, which listens on 0.0.0.0:9887 unless --host and --port say otherwise. The tool set is wider than most Jenkins integrations. Jobs and pipelines: get_item, get_item_config, get_item_parameters, get_all_items, query_items for pattern search, and build_item to trigger. Builds: get_build, get_build_console_output, get_build_parameters, get_build_test_report, get_build_scripts, get_running_builds and stop_build, plus get_all_build_artifacts, get_build_artifact and get_build_artifact_url for pulling artifacts out of a finished run. Queue: get_all_queue_items, get_queue_item, cancel_queue_item. Agents: get_all_nodes, get_node, get_node_config. The plugin tools are the part with no equivalent elsewhere — get_all_plugins, get_plugin, get_plugins_with_updates, get_plugins_with_backup, get_plugin_dependency_graph (Graphviz output), and get_plugins_with_problems, which reports missing dependencies and version mismatches and turns a plugin upgrade audit into one question. Two flags matter for safety. run_groovy_script executes arbitrary Groovy on the controller, which is full remote code execution against your CI; --read-only disables it along with every other mutating tool and is the right default for an agent that only needs to read build state. --jenkins-timeout defaults to 5 seconds, which is often too short for a large get_all_items on a busy controller.
TeamCity MCP
Connect to JetBrains TeamCity CI/CD via REST API — trigger build configurations, monitor build queues, inspect test results, manage agents, and query build artifacts for developer workflow automation.
Sponsored
Better Stack
Free PlanGet alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.
Start monitoring free →