Skip to content
Back to skills

Mcp Setup

ASecurity

MCP server setup and troubleshooting

  • 6 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agentspythonapi

Works with

  • api
  • mcp

Security analysis

A100/100

Scanned November 18, 2026

npx -y skills add AxGord/claude-workflow --skill mcp-setup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mcp Setup?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Mcp Setup
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/axgord-mcp-setup/badge)](https://www.skillsdirectory.com/skills/axgord-mcp-setup)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: mcp-setup
description: MCP server setup and troubleshooting
---

## Rules

1. **NEVER guess package names** → `npm info <name>` to verify before installing
2. **Validate before adding** → `npm info` → `npx -y <pkg> --help` → `claude mcp add`. Caveat: many MCP servers don't implement `--help` and just wait on stdio — wrap validation in `timeout 10 …` so it can't hang.
3. **Think UX upfront** → headless mode, timeouts, flags — ask user BEFORE installing
4. **Restarts**: `/mcp` can reconnect already-registered servers, but registering a NEW server requires a session restart. Get the config right the first time.

## Quick Facts

- Python servers: `claude mcp add <name> -- uvx <pkg>` — uvx launches PyPI packages over stdio, no venv management.
- Remote servers: `claude mcp add --transport http <name> <url>` (also `--transport sse` for legacy SSE servers).
- Scopes: `project` scope lives in `.mcp.json` at the repo root (checked in); `local` scope lives in `~/.claude.json` under that project's entry (NOT in the repo); `user` scope is global in `~/.claude.json`.
- Plugin-bundled servers get tool names `mcp__plugin_<plugin>_<server>__<tool>` — the full name must stay under the 64-char API limit, so keep plugin/server names short.

## Troubleshooting

1. `claude mcp list` for status
2. Run command manually to see error
3. `npm whoami` — fix stale token if needed
4. `npm info <pkg> deprecated` — check if abandoned

## Browser MCP (playwright/chrome-devtools)

- **"Browser is already in use … use --isolated"** = the persistent Chrome profile (`~/Library/Caches/ms-playwright-mcp/mcp-chrome-*` on macOS, `~/.cache/ms-playwright-mcp/mcp-chrome-*` on Linux) is locked by a stale `SingletonLock` symlink (often pointing at an unrelated regular Chrome pid). The MCP server refuses even after `browser_close`.
- **Fix without killing the user's Chrome**: if more than one browser MCP server is configured, each has its own profile — switch to the other server rather than `kill`ing the pid the lock points at (it may be the user's real browser). Stay with ONE browser server per session; alternating between two hits the lock again.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.