Weights & Biases documents a hosted Model Context Protocol server at `https://mcp.withwandb.com/mcp` (recommended) and an open-source `wandb/wandb-mcp-server` package for local stdio or HTTP per docs.wandb.ai/platform/mcp-server. Authenticated clients pass a W&B API key in the `Authorization: Bearer` header. Documented tools include `query_wandb_tool` and `get_run_history_tool` for experiment metrics, `query_weave_traces_tool` and `count_weave_traces_tool` for LLM traces, `create_wandb_report_tool` for markdown reports, `search_wandb_docs_tool` for docs.wandb.ai, and `query_wandb_entity_projects` for project listings. Dedicated/on-prem deployments can set `WANDB_BASE_URL` with the local server per README.
Use cases
- Ask Cursor to query failed Weave traces with `query_weave_traces_tool`
- Pull sampled loss curves via `get_run_history_tool` during debugging
- Generate W&B reports from natural-language prompts
- Search official docs with `search_wandb_docs_tool` while integrating Weave scorers
- Run local MCP with `WANDB_BASE_URL` for dedicated W&B instances
Key features
- Cursor
- Claude Desktop
- Claude Code
- VS Code
- Codex
Frequently Asked Questions
- Should I use hosted or local MCP?
- W&B docs recommend the hosted server at mcp.withwandb.com for fastest setup; local suits air-gapped or dedicated instances.
- Can this replace Langfuse for traces?
- It queries W&B Weave traces and W&B Runs—use if your telemetry already lives in W&B, not as a drop-in for other vendors.
- Is docs search included?
- Yes—`search_wandb_docs_tool` proxies docs.wandb.ai unless disabled with WANDB_MCP_PROXY_DOCS=false.
Related
Related
3 Indexed items
Datadog MCP Server
Datadog documents a remote Model Context Protocol server at docs.datadoghq.com/bits_ai/mcp_server that connects AI agents in Cursor, Claude Code, Codex CLI, VS Code, Gemini CLI, and other MCP clients to observability data across APM, logs, metrics, monitors, dashboards, and security signals. Setup guides describe OAuth-based connection to Datadog's hosted MCP endpoint (distinct from the local-only Code Security MCP Server used for SAST/SCA scans). Fair-use limits listed in docs include 50 requests per 10 seconds burst and 50,000 monthly tool calls; Audit Trail records MCP actions with tool name, arguments, user identity, and client, while metrics `datadog.mcp.session.starts` and `datadog.mcp.tool.usage` tag usage by client and tool.
LangSmith MCP Server
LangChain documents a LangSmith Model Context Protocol server that lets MCP clients read conversation threads, prompts, runs and traces, datasets, experiments, and billing usage from a LangSmith workspace. For LangSmith Cloud, docs recommend the OAuth-authenticated LangSmith Remote MCP (regional endpoints on api.smith.langchain.com and documented EU/APAC/AWS variants) with the same tool surface and no separate deployment. The standalone HTTP server at https://langsmith-mcp-server.onrender.com/mcp remains documented for API-key access via the LANGSMITH-API-KEY header, while self-hosted LangSmith users can run the open-source langsmith-mcp-server package with uvx, Docker HTTP on port 8000, or point LANGSMITH_ENDPOINT at private instances. Tools include get_thread_history, list_prompts, fetch_runs (with FQL filters and character-budget pagination), dataset/example readers, list_experiments, and get_billing_usage per the official tool table.
Mem0 MCP Server
Mem0 documents a hosted Model Context Protocol server at https://mcp.mem0.ai/mcp that exposes Platform memory tools (`add_memory`, `search_memories`, `get_memories`, `update_memory`, `delete_memory`, `delete_all_memories`, `delete_entities`, `list_entities`, `list_events`, `get_event_status`) to Claude, Claude Code, Codex, Cursor, Windsurf, VS Code, and OpenCode. Setup uses `npx mcp-add` with HTTP transport or manual JSON/TOML client configs; Codex requires `MEM0_API_KEY` as bearer token per docs.mem0.ai/platform/mem0-mcp. The cloud server needs a Mem0 Platform API key from the dashboard and Node.js for the installer—no local vector database required for the hosted path.