scriptoriumadmin/claude-skills
1
0
Fork 0
mirror of https://github.com/alirezarezvani/claude-skills.git synced 2026-08-28 04:24:58 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs(pw): propagate 'MCP servers not auto-registered' caveat to remaining docs (#978)

Browse source 
Addresses review feedback on #981: README.md, skills/pw/SKILL.md, and the
testrail/browserstack SKILL.md files still described the integrations as working
after just exporting env vars. Add a caveat to each that pw-testrail/pw-browserstack
are no longer auto-registered and that /pw:testrail // /pw:browserstack (and the
testrail_*/browserstack_* MCP tools) fail with 'tool not found' until the server is
enabled manually, pointing to the CLAUDE.md Integrations section.
This commit is contained in:
Claude 2026-08-24 18:40:19 +00:00
parent bde43b44bc
commit d655976ccf
No known key found for this signature in database
4 changed files with 32 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
engineering-team/playwright-pro/README.md
View file

@ -80,6 +80,14 @@ Ready-to-use, parametrizable templates covering:
## Integrations Setup
> **Note (issue #978):** the TestRail and BrowserStack MCP servers are **not
> auto-registered** — they were removed from the plugin's `.mcp.json` because they
> failed to connect for every user (no bundled `node_modules`). Setting the env
> vars below is **not** enough on its own; `/pw:testrail` and `/pw:browserstack`
> will fail with "tool not found" until you enable the server manually
> (`cd integrations/<name>-mcp && npm install`, then register it in your own
> user/project MCP config). See the **Integrations** section of `CLAUDE.md`.
### TestRail (Optional)
Set environment variables:

9
engineering-team/playwright-pro/skills/browserstack/SKILL.md
View file

@ -18,6 +18,15 @@ Environment variables must be set:
If not set, inform the user how to get them from [browserstack.com/accounts/settings](https://www.browserstack.com/accounts/settings) and stop.
> **The BrowserStack MCP server is not auto-registered (issue #978).**
> `pw-browserstack` was removed from the plugin's `.mcp.json` because it failed to
> connect for every user (the plugin ships no `node_modules`). The `browserstack_*`
> MCP tools used below, and the `/pw:browserstack` command, will fail with "tool
> not found" until it is enabled manually — see the **Integrations** section of the
> plugin's `CLAUDE.md` (`cd integrations/browserstack-mcp && npm install`, then
> register the server in your own user/project MCP config). Setting the env vars
> alone is not sufficient.
## Capabilities
### 1. Configure for BrowserStack

7
engineering-team/playwright-pro/skills/pw/SKILL.md
View file

@ -98,6 +98,13 @@ npx playwright test tests/auth/login.spec.ts --headed
## Integration Setup
> **Not auto-registered (issue #978).** The TestRail and BrowserStack MCP servers
> are no longer declared in the plugin's `.mcp.json` (they failed to connect for
> every user — no bundled `node_modules`). Exporting the env vars below is not
> enough: `/pw:testrail` / `/pw:browserstack` fail with "tool not found" until you
> enable the server manually (`cd integrations/<name>-mcp && npm install`, then
> register it in your own user/project MCP config). See `CLAUDE.md` → Integrations.
### TestRail (Optional)
```bash
export TESTRAIL_URL="https://your-instance.testrail.io"

8
engineering-team/playwright-pro/skills/testrail/SKILL.md
View file

@ -19,6 +19,14 @@ Environment variables must be set:
If not set, inform the user how to configure them and stop.
> **The TestRail MCP server is not auto-registered (issue #978).** `pw-testrail`
> was removed from the plugin's `.mcp.json` because it failed to connect for every
> user (the plugin ships no `node_modules`). The `testrail_*` MCP tools used below,
> and the `/pw:testrail` command, will fail with "tool not found" until it is
> enabled manually — see the **Integrations** section of the plugin's `CLAUDE.md`
> (`cd integrations/testrail-mcp && npm install`, then register the server in your
> own user/project MCP config). Setting the env vars alone is not sufficient.
## Capabilities
### 1. Import Test Cases → Generate Playwright Tests