Skip to main content

Overview

MCP (Model Context Protocol) servers extend Claude Code with external integrations for GitHub, databases, deployment platforms, and more. ECC includes 14 pre-configured MCP servers.

Available MCP Servers

Development Tools

GitHub

Setup:
  1. Create a GitHub Personal Access Token at github.com/settings/tokens
  2. Replace YOUR_GITHUB_PAT_HERE with your token
  3. Scopes needed: repo, read:org, workflow

Firecrawl

Setup: Get an API key from firecrawl.dev

Database & Backend

Supabase

Setup: Get your project ref from Supabase dashboard settings

ClickHouse

PostgreSQL (via Filesystem)

Deployment Platforms

Vercel

Railway

Cloudflare Services

Cloudflare Documentation

Cloudflare Workers Builds

Cloudflare Workers Bindings

Cloudflare Observability

AI & Enhancement

Memory

Sequential Thinking

Context7

Setup: Get an API key from exa.ai

UI Components

Magic UI

Installation

MCP servers are configured in ~/.claude.json (not settings.json):

Context Window Management

Critical: Each MCP tool description consumes tokens from your 200k window, potentially reducing it to ~70k.

Best Practices

  • Keep under 10 MCPs enabled per project
  • Keep under 80 tools active total
  • Disable unused MCPs per project using disabledMcpServers

Disabling MCPs Per Project

Create .claude/settings.json in your project:
This disables those MCPs for this project only, preserving context window space.

Security Notes

Never commit API keys to version control. Always use environment variables or a secret manager.
  • Replace all YOUR_*_HERE placeholders with actual values
  • Use environment variables for sensitive keys
  • Add .claude.json to .gitignore if it contains secrets
  • Rotate any exposed secrets immediately