Configuration de MCP
/SKILLConfigurer les serveurs MCP les plus courants pour améliorer les fonctionnalités des agents
name: mcp-setup
description: Configure popular MCP servers for enhanced agent capabilities
level: 2
MCP Setup
Configure Model Context Protocol (MCP) servers to extend Claude Code's capabilities with external tools like web search, file system access, and GitHub integration.
Overview
MCP servers provide additional tools that Claude Code agents can use. This skill helps you configure popular MCP servers using the claude mcp add command-line interface.
Step 1: Choose a Setup Path
Use AskUserQuestion with one question at a time and no more than 3 options per question. Recent Claude Code builds reject larger option payloads as invalid tool parameters, so keep the MCP selection flow staged.
Step 1.1: First menu
Question: "What kind of MCP setup would you like?"
Options:
- Recommended starter setup - Fast path for the most common OMC MCP additions
- Individual popular server - Pick one built-in server from a short follow-up menu
- Custom server - Add your own stdio or HTTP MCP server
Step 1.2: If the user chooses "Recommended starter setup"
Ask a follow-up AskUserQuestion:
Question: "Which recommended MCP bundle should I configure?"
Options:
- Context7 only (Recommended) - Zero-config docs/context server
- Context7 + Exa - Docs/context plus enhanced web search
- Full recommended bundle - Context7, Exa, Filesystem, and GitHub
Map that choice to the server list you will configure.
Step 1.3: If the user chooses "Individual popular server"
Ask a follow-up AskUserQuestion:
Question: "Which server should I configure first?"
Options:
- Context7 (Recommended) - Documentation and code context from popular libraries
- Exa Web Search - Enhanced web search (replaces built-in websearch)
- More server choices - Filesystem, GitHub, or the full recommended bundle
If the user chooses More server choices, ask one more AskUserQuestion:
Question: "Which additional MCP option do you want?"
Options:
- Filesystem (Recommended) - Extended file system access with additional capabilities
- GitHub - GitHub API integration for issues, PRs, and repository management
- Full recommended bundle - Configure Context7, Exa, Filesystem, and GitHub together
Step 1.4: If the user chooses "Custom server"
Skip directly to the Custom MCP Server section below.
Step 2: Gather Required Information
For Context7:
No API key required. Ready to use immediately.
For Exa Web Search:
Ask for API key:
Do you have an Exa API key?
- Get one at: https://exa.ai
- Enter your API key, or type 'skip' to configure laterFor Filesystem:
Ask for allowed directories:
Which directories should the filesystem MCP have access to?
Default: Current working directory
Enter comma-separated paths, or press Enter for defaultFor GitHub:
Ask for token:
Do you have a GitHub Personal Access Token?
- Create one at: https://github.com/settings/tokens
- Recommended scopes: repo, read:org
- Enter your token, or type 'skip' to configure laterStep 3: Add MCP Servers Using CLI
Use the claude mcp add command to configure each MCP server. The CLI automatically handles settings.json updates and merging.
Context7 Configuration:
claude mcp add context7 -- npx -y @upstash/context7-mcpExa Web Search Configuration:
claude mcp add -e EXA_API_KEY=<user-provided-key> exa -- npx -y exa-mcp-serverFilesystem Configuration:
claude mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem <allowed-directories>GitHub Configuration:
Option 1: Docker (local)
claude mcp add -e GITHUB_PERSONAL_ACCESS_TOKEN=<user-provided-token> github -- docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/github/github-mcp-serverOption 2: HTTP (remote)
claude mcp add --transport http github https://api.githubcopilot.com/mcp/Note: Docker option requires Docker installed. HTTP option is simpler but may have different capabilities.
Step 4: Verify Installation
After configuration, verify the MCP servers are properly set up:
# List configured MCP servers
claude mcp listThis will display all configured MCP servers and their status.
Step 5: Show Completion Message
MCP Server Configuration Complete!
CONFIGURED SERVERS:
[List the servers that were configured]
NEXT STEPS:
1. Restart Claude Code for changes to take effect
2. The configured MCP tools will be available to all agents
3. Run `claude mcp list` to verify configuration
USAGE TIPS:
- Context7: Ask about library documentation (e.g., "How do I use React hooks?")
- Exa: Use for web searches (e.g., "Search the web for latest TypeScript features")
- Filesystem: Extended file operations beyond the working directory
- GitHub: Interact with GitHub repos, issues, and PRs
TROUBLESHOOTING:
- If MCP servers don't appe