How to Configure MCP Servers for Everything Claude Code: A Complete Guide

Configure MCP servers for Everything Claude Code by copying entries from mcp-configs/mcp-servers.json into your ~/.claude.json file, replacing placeholder API keys with real credentials, and optionally disabling unused servers via disabledMcpServers to preserve context window space.

Everything Claude Code extends Claude's capabilities through Model Context Protocol (MCP) servers—external services that enable GitHub operations, web scraping, database queries, and more. This guide shows you how to configure MCP servers based on the official source files in the WorldFlowAI/everything-claude-code repository.

Understanding MCP Server Configuration

MCP servers in Everything Claude Code follow a JSON-based configuration schema. The repository maintains a master list in mcp-configs/mcp-servers.json that serves as your starting template.

MCP Server JSON Schema

Each server entry under the mcpServers key supports two execution models:

Field	Purpose	Required For
command	Executable to start the server (typically npx)	Command-based servers
args	Arguments passed to the command including package name	Command-based servers
env	Environment variables for API keys and credentials	Servers needing authentication
type	Set to "http" for remote servers only	HTTP-based servers
url	Base URL for HTTP server endpoints	HTTP-based servers
description	Human-readable service description	All entries

Step-by-Step MCP Server Setup

Step 1: Copy Server Definitions

Locate the desired server entry in mcp-configs/mcp-servers.json. The file contains pre-configured servers including GitHub, Firecrawl, Supabase, Vercel, Railway, Cloudflare, and ClickHouse.

Step 2: Paste Into Your Claude Configuration

Copy entries into ~/.claude.json under the mcpServers section. According to the repository README, your personal config file follows this structure:

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "YOUR_GITHUB_PAT_HERE"
      },
      "description": "GitHub operations - PRs, issues, repos"
    }
  }
}

Step 3: Replace Placeholder Credentials

The README emphasizes: "Replace YOUR_*_HERE placeholders with your actual API keys." Common placeholders include:

• YOUR_GITHUB_PAT_HERE → GitHub personal access token
• YOUR_FIRECRAWL_KEY_HERE → Firecrawl API key
• YOUR_PROJECT_REF → Supabase project reference

Step 4: Disable Unused Servers

Add unneeded server keys to disabledMcpServers to prevent context window consumption:

{
  "disabledMcpServers": [
    "cloudflare-observability",
    "clickhouse",
    "railway"
  ]
}

MCP Server Execution Models

Everything Claude Code supports two server types with identical JSON schemas:

Command-based servers launch local processes via npx. Claude Code starts these on demand when you invoke their tools.

HTTP-based servers connect to remote endpoints directly. Set type: "http" and provide the url field:

{
  "mcpServers": {
    "vercel": {
      "type": "http",
      "url": "https://mcp.vercel.com",
      "description": "Vercel deployments and projects"
    }
  }
}

Context Window Management Best Practices

The repository README warns: "Keep under 10 MCPs enabled to preserve context window."

Each enabled MCP consumes tokens from Claude's available context. Exceeding this threshold degrades performance significantly. Use the disabledMcpServers array to stay within the recommended limit of approximately 10 active servers per project.

Practical Configuration Examples

GitHub and Supabase Setup

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_xxxxxxxxxxxxxxxx" },
      "description": "GitHub operations"
    },
    "supabase": {
      "command": "npx",
      "args": ["-y", "@supabase/mcp-server-supabase@latest", "--project-ref=abcdefgh12345678"],
      "description": "Supabase database operations"
    }
  }
}

Source: Lines 4-9 (github) and lines 19-22 (supabase) in mcp-configs/mcp-servers.json

Custom HTTP Server Addition

{
  "mcpServers": {
    "internal-api": {
      "type": "http",
      "url": "https://api.internal.company.com/mcp",
      "description": "Internal asset lookup service"
    }
  }
}

Pattern reference: vercel, railway, and cloudflare-* entries in mcp-configs/mcp-servers.json

Key Repository Files for MCP Configuration

File	Purpose	Location
mcp-configs/mcp-servers.json	Master template with all pre-configured MCP servers	mcp-configs/mcp-servers.json
README.md	Configuration instructions and context window warnings	README.md
examples/CLAUDE.md	Full project-level config example	examples/CLAUDE.md
hooks/hooks.json	Hook definitions that may reference MCP servers	hooks/hooks.json

Summary

• Primary configuration source: Copy from mcp-configs/mcp-servers.json in the Everything Claude Code repository
• Personal config location: ~/.claude.json with mcpServers and optional disabledMcpServers sections
• Credential requirement: Replace all YOUR_*_HERE placeholders with actual API keys before use
• Performance limit: Enable maximum 10 MCP servers to preserve context window efficiency
• Execution flexibility: Choose between local command/args servers or remote http/url endpoints

Frequently Asked Questions

Where do I store my MCP server configuration for Everything Claude Code?

Store your active MCP configuration in ~/.claude.json under the mcpServers key. This personal configuration file merges with project-level settings. Copy server definitions from the repository's mcp-configs/mcp-servers.json template as your starting point.

Why should I disable MCP servers I'm not using?

Disabled servers via disabledMcpServers prevent context window consumption. Each enabled MCP reserves tokens from Claude's available context. The repository README recommends keeping under 10 active servers to maintain optimal performance and response quality.

How do I add a custom MCP server not in the repository template?

Define your custom server using the same JSON schema in ~/.claude.json. For local servers, use command and args fields with npx. For remote services, set type: "http" and provide the url endpoint. Include a description field for clarity and env if authentication is required.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}