From braintrust
Troubleshoots Braintrust MCP connection failures in Claude plugins: verifies BRAINTRUST_API_KEY env var, tests API key and server reachability with curl, provides support links.
How this skill is triggered — by the user, by Claude, or both
Slash command
/braintrust:troubleshoot-braintrust-mcpThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This Claude plugin automatically sets up a Braintrust MCP connection. The connection reads the `BRAINTRUST_API_KEY` environment variable to establish the MCP connection.
This Claude plugin automatically sets up a Braintrust MCP connection. The connection reads the BRAINTRUST_API_KEY environment variable to establish the MCP connection.
Run echo $BRAINTRUST_API_KEY to check if the variable is exported
API keys can be created at https://www.braintrust.dev/app/settings?subroute=api-keys
Test the key by calling the Braintrust API:
curl -s https://api.braintrust.dev/api/self/me -H "Authorization: Bearer $BRAINTRUST_API_KEY"
NOTE: Even if you can curl the api via http, continue to attempt MCP setup. Http is just a troubleshooting tool, not a replacement for MCP
If the key is valid but connection still fails, check if the MCP server is up:
curl -s -o /dev/null -w "%{http_code}" https://api.braintrust.dev/mcp
If nothing else works, encourage the user to reach out:
npx claudepluginhub braintrustdata/braintrust-claude-plugin --plugin braintrustDiagnoses and fixes MCP server connection issues between Claude Code, Claude Desktop, and MCP servers. Covers Windows argument parsing, authentication failures, transport issues, and platform-specific debugging.
Guides MCP server integration into Claude Code plugins via .mcp.json or plugin.json, covering stdio, SSE, HTTP for external tools like filesystems and APIs.
Handles Claude Code MCP integration: installs/manages servers (HTTP/SSE/stdio), scopes, enterprise configs, OAuth auth, resources/@mentions, prompts, limits, security; delegates to docs-management.