claude-skills/engineering-team/playwright-pro/integrations/mcp-servers.example.json
Claude bf005356e0
fix(playwright-pro): make TestRail/BrowserStack MCP servers opt-in instead of always-failing (#978)
The two MCP servers registered in .mcp.json could never start: their
@modelcontextprotocol/sdk dependency is declared but never installed
(the plugin ships no node_modules and nothing runs npm install), so every
user saw a permanent 'Failed to connect' pair in `claude mcp list`.

Per the reporter's option 4 + docs: the registrations move to
integrations/mcp-servers.example.json (no longer auto-loaded), and the
README's Integrations Setup section now documents the two-step opt-in
(npm install inside the integration folder, copy the example to .mcp.json).
The integrations themselves are unchanged and keep working for users who
enable them.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qgc6RYXWJPr5oW9DHU7zR4
2026-08-24 18:28:45 +00:00

27 lines
668 B
JSON

{
"mcpServers": {
"pw-testrail": {
"command": "npx",
"args": [
"tsx",
"${CLAUDE_PLUGIN_ROOT}/integrations/testrail-mcp/src/index.ts"
],
"env": {
"TESTRAIL_URL": "${TESTRAIL_URL}",
"TESTRAIL_USER": "${TESTRAIL_USER}",
"TESTRAIL_API_KEY": "${TESTRAIL_API_KEY}"
}
},
"pw-browserstack": {
"command": "npx",
"args": [
"tsx",
"${CLAUDE_PLUGIN_ROOT}/integrations/browserstack-mcp/src/index.ts"
],
"env": {
"BROWSERSTACK_USERNAME": "${BROWSERSTACK_USERNAME}",
"BROWSERSTACK_ACCESS_KEY": "${BROWSERSTACK_ACCESS_KEY}"
}
}
}
}