MCP Server
The Skillsmith MCP server integrates directly with Claude Code, enabling natural language skill discovery and management.
Overview
MCP (Model Context Protocol) servers extend Claude's capabilities by providing additional tools. The Skillsmith MCP server adds tools for searching, installing, and managing Claude Code skills.
Configuration
Basic Setup
Add Skillsmith to your Claude settings at ~/.claude/settings.json:
{
"mcpServers": {
"skillsmith": {
"command": "npx",
"args": ["-y", "@skillsmith/mcp-server"]
}
}
} Advanced Configuration
For more control, you can specify additional options:
{
"mcpServers": {
"skillsmith": {
"command": "npx",
"args": ["-y", "@skillsmith/mcp-server"],
"env": {
"SKILLSMITH_LOG_LEVEL": "debug",
"SKILLSMITH_CACHE_TTL": "3600"
}
}
}
} API Key Configuration
The Skillsmith API provides access to 14,000+ skills that are indexed daily from GitHub and security screened hourly for vulnerabilities. Configure your API key for higher rate limits and usage tracking.
Why Use an API Key?
- Live indexed skills - Access skills as they're discovered and screened
- Higher rate limits - Up to 300 requests/minute on Enterprise tier
- Usage dashboard - Track your API usage at skillsmith.app/account
- Priority access - During high-traffic periods
Setup
Step 1: Create an account and get your API key at skillsmith.app/account
Step 2: Configure your API key using one of these methods:
Method A: Config File (Recommended)
Create ~/.skillsmith/config.json - works on all platforms:
mkdir -p ~/.skillsmith && cat > ~/.skillsmith/config.json << 'EOF'
{
"apiKey": "sk_live_your_key_here"
}
EOF Method B: Claude Settings
Add to your ~/.claude/settings.json:
{
"mcpServers": {
"skillsmith": {
"command": "npx",
"args": ["-y", "@skillsmith/mcp-server"],
"env": {
"SKILLSMITH_API_KEY": "sk_live_your_key_here"
}
}
}
} Step 3: Restart Claude Code (Cmd/Ctrl+Shift+P → "Claude Code: Restart")
Security Note
Never paste your API key directly in chat. Always configure it via one of the methods above. Your key will be used automatically for all Skillsmith API requests.
Shell Exports Don't Work
Running export SKILLSMITH_API_KEY=... in your terminal does NOT pass the variable
to MCP servers. MCP servers run as subprocesses spawned by Claude Code and don't inherit your
shell environment. Use the config file or settings.json method above.
Rate Limits by Tier
| Tier | Rate Limit | Monthly Cost | Best For |
|---|---|---|---|
| Trial | 10 total | Free | Quick evaluation |
| Community | 30/min | Free | Personal projects |
| Individual | 60/min | $9.99/mo | Active developers |
| Team | 120/min | $25/user/mo | Development teams |
| Enterprise | 300/min | $55/user/mo | Large organizations |
Other Environment Variables
| Variable | Description | Default |
|---|---|---|
SKILLSMITH_LOG_LEVEL | Logging level (debug, info, warn, error) | info |
SKILLSMITH_CACHE_TTL | Cache time-to-live in seconds | 1800 |
SKILLSMITH_REGISTRY | Custom registry URL | default registry |
SKILLSMITH_API_KEY | Personal API key for usage tracking | - |
Available Tools
The MCP server provides the following tools to Claude:
search
Search for skills in the registry.
// Tool: search
// Parameters:
{
"query": "testing", // Search term (required)
"category": "development", // Category filter
"trust_tier": "verified", // Trust tier filter
"min_score": 70, // Minimum quality score
"limit": 10 // Max results
} Example prompts:
- "Search for testing skills"
- "Find verified skills for git workflows"
- "Show me devops skills with high quality scores"
get_skill
Get detailed information about a specific skill.
// Tool: get_skill
// Parameters:
{
"id": "community/jest-helper" // Skill ID (required)
} Example prompts:
- "Show details for community/jest-helper"
- "What does the git-commit skill do?"
install_skill
Install a skill to the local environment.
// Tool: install_skill
// Parameters:
{
"id": "community/jest-helper", // Skill ID (required)
"path": "~/.claude/skills", // Installation path
"force": false // Overwrite existing
} Example prompts:
- "Install the jest-helper skill"
- "Install community/git-commit"
uninstall_skill
Remove an installed skill.
// Tool: uninstall_skill
// Parameters:
{
"id": "community/jest-helper" // Skill ID (required)
} Example prompts:
- "Uninstall the jest-helper skill"
- "Remove community/git-commit"
recommend
Get personalized skill recommendations.
// Tool: recommend
// Parameters:
{
"context": "react", // Technology context
"limit": 5 // Max recommendations
} Example prompts:
- "Recommend skills for my React project"
- "What skills would help with Node.js development?"
compare
Compare multiple skills side-by-side.
// Tool: compare
// Parameters:
{
"skill_ids": ["jest-helper", "vitest-helper"] // 2-5 skill IDs
} Example prompts:
- "Compare jest-helper and vitest-helper"
- "What's the difference between these testing skills?"
validate
Validate a skill's structure.
// Tool: validate
// Parameters:
{
"path": "./my-skill" // Path to skill directory
} Example prompts:
- "Validate my skill at ./my-skill"
- "Check if this skill structure is correct"
Usage Examples
Discovering Skills
You: "I need help with testing in my project. What skills are available?"
Claude: [Uses search tool] I found several testing skills:
- jest-helper: Comprehensive Jest testing utilities
- vitest-helper: Vitest integration and helpers
- playwright-utils: End-to-end testing with Playwright
... Installing and Using Skills
You: "Install the jest-helper skill and show me how to use it"
Claude: [Uses install_skill tool] I've installed jest-helper to
~/.claude/skills/jest-helper. This skill provides... Comparing Options
You: "Should I use jest-helper or vitest-helper for my Vite project?"
Claude: [Uses compare tool] Here's a comparison:
| Feature | jest-helper | vitest-helper |
| Vite support | Limited | Native |
| Speed | Moderate | Fast |
... Trust Tiers
| Tier | Description | Review Process |
|---|---|---|
verified | Official Anthropic skills | Full security audit |
community | Community-reviewed | Peer review + automated checks |
experimental | Beta/new skills | Basic validation only |
unknown | Unverified | None |
Troubleshooting
Server Not Starting
Check Node.js Version
Ensure you have Node.js 18+ installed. Run node --version to verify.
Tools Not Available
Verify Configuration
Ensure your ~/.claude/settings.json is valid JSON and the
MCP server configuration is correct. Restart Claude Code after changes.
Enable Debug Logging
{
"mcpServers": {
"skillsmith": {
"command": "npx",
"args": ["-y", "@skillsmith/mcp-server"],
"env": {
"SKILLSMITH_LOG_LEVEL": "debug"
}
}
}
}