# MCP Setup > Configure popular MCP servers for enhanced agent capabilities - Skill: `materialofair/mcp-setup` (Agent Skill) - Install (CLI): `npx skillmds@latest add materialofair/mcp-setup` - Raw SKILL.md: https://api.skillmd.com/api/skills/materialofair/mcp-setup/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: materialofair (https://skillmd.com/u/materialofair) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/materialofair/mcp-setup --- # MCP Setup ## Codex Quickstart Codex uses `~/.codex/config.toml` for MCP servers. Use one of: ``` ./scripts/generate-codex-mcp-config.sh ``` Or manage via CLI: ``` codex mcp add codex mcp list ``` Related 0.9+ helpers: ``` /apps # browse connected apps/connectors /debug-config # inspect active Codex config and MCP wiring ``` Approval tip: for trusted MCP tools, use "allow and remember" to avoid repeated prompts in the same workflow. ## Native Subagent Protocol (Codex) Codex supports native subagents. Delegate with `spawn_agent`, coordinate with `send_input`, collect via `wait_agent`, and clean up with `close_agent`. Execution preference: 1. Use native subagents first for independent workstreams (parallel when possible). 2. Merge results in main thread and run final verification. 3. Fallback only when delegation is blocked: use the `[ANALYST]`/`[ARCHITECT]`/`[EXECUTOR]`/`[REVIEWER]` structure in a single response. Minimal orchestration pattern: ```text spawn_agent -> send_input (optional) -> wait_agent -> close_agent ``` > Codex invocation: use `$mcp-setup ...` or `mcp-setup: ...` Configure Model Context Protocol (MCP) servers to extend Codex's capabilities with external tools like web search, file system access, and GitHub integration. ## Overview MCP servers provide additional tools that Codex agents can use. This skill helps you configure popular MCP servers using the `codex mcp add` command-line interface. ## Step 1: Show Available MCP Servers Present the user with available MCP server options in plain text with numbered choices: **Question:** "Which MCP server would you like to configure?" **Options:** 1. **Context7** - Documentation and code context from popular libraries 2. **Exa Web Search** - Enhanced web search (replaces built-in websearch) 3. **Filesystem** - Extended file system access with additional capabilities 4. **GitHub** - GitHub API integration for issues, PRs, and repository management 5. **All of the above** - Configure all recommended MCP servers 6. **Custom** - Add a custom MCP server ## 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 later ``` ### For 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 default ``` ### For 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 later ``` ## Step 3: Add MCP Servers Using CLI Use the `codex mcp add` command to configure each MCP server. ### Context7 Configuration: ```bash codex mcp add context7 -- npx -y @upstash/context7-mcp ``` ### Exa Web Search Configuration: ```bash codex mcp add -e EXA_API_KEY= exa -- npx -y exa-mcp-server ``` ### Filesystem Configuration: ```bash codex mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem ``` ### GitHub Configuration: **Option 1: Docker (local)** ```bash codex mcp add -e GITHUB_PERSONAL_ACCESS_TOKEN= github -- docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/github/github-mcp-server ``` **Option 2: HTTP (remote)** ```bash codex 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: ```bash # List configured MCP servers codex mcp list ``` This 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 Codex for changes to take effect 2. The configured MCP tools will be available to all agents 3. Run `codex 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 appear, run `codex mcp list` to check status - Ensure you have Node.js 18+ installed for npx-based servers - For GitHub Docker option, ensure Docker is installed and running - Run $doctor to diagnose issues MANAGING MCP SERVERS: - Add more servers: $mcp-setup or `codex mcp add ...` - List servers: `codex mcp list` - Remove a server: `codex mcp remove ` ``` ## Custom MCP Server If user selects "Custom": Ask for: 1. Server name (identifier) 2. Transport type: `stdio` (default) or `http` 3. For stdio: Command and arguments (e.g., `npx my-mcp-server`) 4. For http: URL (e.g., `https://example.com/mcp`) 5. Environment variables (optional, key=value pairs) 6. HTTP headers (optional, for http transport only) Then construct and run the appropriate `codex mcp add` command: **For stdio servers:** ```bash # Without environment variables codex mcp add -- [args...] # With environment variables codex mcp add -e KEY1=value1 -e KEY2=value2 -- [args...] ``` **For HTTP servers:** ```bash # Basic HTTP server codex mcp add --transport http # HTTP server with headers codex mcp add --transport http --header "Authorization: Bearer " ``` ## Common Issues ### MCP Server Not Loading - Ensure Node.js 18+ is installed - Check that npx is available in PATH - Run `codex mcp list` to verify server status - Check server logs for errors ### API Key Issues - Exa: Verify key at https://dashboard.exa.ai - GitHub: Ensure token has required scopes (repo, read:org) - Re-run `codex mcp add` with correct credentials if needed ### Agents Still Using Built-in Tools - Restart Codex after configuration - The built-in websearch will be deprioritized when exa is configured - Run `codex mcp list` to confirm servers are active ### Removing or Updating a Server - Remove: `codex mcp remove ` - Update: Remove the old server, then add it again with new configuration