Install MCP Skills Claude Code Mac: CLI & Manual Methods
Install MCP skills for Claude Code on Mac using the CLI or manual config editing. Covers global vs project scope, NVM path fixes, and how to verify tools are loading correctly.
🕐Last updated 4 March 2026
Run claude mcp add weather -- npx -y @trustedskills/weather-mcp — done. Or edit ~/.claude/settings.json manually. If you're using nvm and Claude can't find npx, use the full path from which npx.
When I set this up on my Mac, I used the CLI method and had a working skill in about 45 seconds. The manual method is also fine — good to know for when you want to add environment variables or tweak things the CLI doesn't expose easily.
Prerequisites
- Node.js installed — verify with
node --version - Claude Code CLI:
npm install -g @anthropic-ai/claude-code
Method 1: CLI (Recommended)
# Global — available in every project
claude mcp add weather -- npx -y @trustedskills/weather-mcp
# Project-scoped — current directory only
claude mcp add weather --project -- npx -y @trustedskills/weather-mcp
# With an env variable (API key, etc.)
claude mcp add my-api -e API_KEY=yourkey -- npx -y @trustedskills/my-api-mcp
# See what's installed
claude mcp list
# Remove something
claude mcp remove weatherMethod 2: Manual Config Edit
mkdir -p ~/.claude
code ~/.claude/settings.json # VS Code
# or
open -e ~/.claude/settings.json # TextEdit (use Format → Plain Text first){
"mcpServers": {
"weather": {
"command": "npx",
"args": ["-y", "@trustedskills/weather-mcp"]
}
}
}The nvm Problem on Mac
nvm is great for managing Node versions — but Claude Code sometimes can't find the npx that nvm manages, because nvm configures PATH only for interactive shell sessions.
# Find the full path to npx
which npx
# /Users/yourname/.nvm/versions/node/v20.11.0/bin/npx{
"mcpServers": {
"weather": {
"command": "/Users/yourname/.nvm/versions/node/v20.11.0/bin/npx",
"args": ["-y", "@trustedskills/weather-mcp"]
}
}
}The most reliable fix we've found for the nvm issue: create a symlink from a stable location to the current nvm npx. ln -sf $(which npx) /usr/local/bin/npx. Now you can use /usr/local/bin/npx in all your configs — and it automatically follows whichever nvm version you switch to.
Verify It Worked
claude mcp list # see configured skills
claude # start a session
/tools # list available toolsFrequently Asked Questions
CLI vs manual editing — which should I use?
CLI for quick additions — it handles JSON formatting and reloads the connection automatically. Manual editing for complex configs with multiple env variables, specific version pins, or when you want to review exactly what's stored.
How do I add an API key to a skill on Mac?
With the CLI: claude mcp add my-skill -e API_KEY=abc123 -- npx -y @package/name. Manually: add an "env" block to the skill's entry in settings.json.
How do I know a skill loaded successfully?
Run claude mcp list to see configured skills. Start Claude with claude and type /tools — if the skill's tools appear, it loaded. If they don't, something went wrong at launch.
TrustedSkills Team
The TrustedSkills team builds and tests AI agent integrations across Claude, OpenClaw, Cursor, and VS Code. We verify every skill in our registry and have set up hundreds of MCP configs across every major platform.