MCP Server Integration

Overview

MCP (Model Context Protocol) servers extend Claude Code's capabilities by connecting it to external tools and data sources. Instead of copy-pasting data into prompts, MCP lets Claude query databases, read documentation, interact with APIs, and use specialized tools directly.

Why This Matters

• -Direct data access — Claude queries your database instead of you describing schemas
• -Tool integration — GitHub, Slack, Jira operations without leaving Claude Code
• -Real-time context — Claude reads live documentation and API specs
• -Custom tools — build MCP servers for your team's specific workflows

How It Works

Step 1: Configure .mcp.json

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/docs"]
    },
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_..."
      }
    },
    "postgres": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-postgres"],
      "env": {
        "DATABASE_URL": "postgresql://user:pass@localhost:5432/mydb"
      }
    }
  }
}

Step 2: Place Configuration

# Project-level (recommended for team sharing)
# Place .mcp.json at the project root

# User-level (personal integrations)
# Place in ~/.claude/.mcp.json

Step 3: Verify Connection

# Claude Code automatically discovers MCP servers on startup
# Ask Claude to list available tools to verify
> "What MCP tools are available?"

Step 4: Use in Workflows

# Claude can now directly:
- Query your PostgreSQL database for schema information
- Read and create GitHub issues and PRs
- Access files in specified directories
- Use any custom tools your MCP servers expose

Popular MCP Servers

Best Practices

• -Use project-level .mcp.json for team-shared integrations
• -Store credentials in environment variables, not directly in .mcp.json
• -Add .mcp.json to .gitignore if it contains secrets (provide .mcp.json.example instead)
• -Limit filesystem server access to specific directories (principle of least privilege)
• -Test MCP connections before relying on them in critical workflows

Common Mistakes

• -Committing .mcp.json with real credentials to version control
• -Giving filesystem MCP access to the entire disk
• -Not handling MCP server startup failures gracefully
• -Using too many MCP servers simultaneously (slows startup)