Skip to main content

MCP Components

MCPs (Model Context Protocol servers) enable Claude Code to integrate with external services, databases, APIs, and tools. They extend Claude’s capabilities beyond the local codebase.

Browse All MCPs

Explore 65+ MCP integrations at aitmpl.com

Installation

MCP Categories

Database MCPs

Connect to databases and manage data:

Neon

Neon serverless Postgres integration
Features:
  • Query databases directly
  • Manage schemas and migrations
  • Access Neon Management API

Supabase

Supabase platform integration
Features:
  • Database operations
  • Authentication management
  • Storage and realtime

PostgreSQL

Direct PostgreSQL database access

MySQL

MySQL database integration

MCP Configuration

MCPs are configured in .claude/.mcp.json:

How MCPs Work

  1. Installation: MCP configuration is added to .mcp.json
  2. Startup: Claude Code loads configured MCPs on launch
  3. Tool Access: MCPs expose tools that Claude can use
  4. Execution: When Claude uses an MCP tool, it communicates with the external service

Environment Variables

Many MCPs require API keys or credentials:

Example Usage

Neon

Serverless Postgres with branching, instant provisioning, and autoscaling.

Supabase

Complete backend platform with database, auth, storage, and realtime.

Web Fetch

Fetch and parse web content for research and analysis.

GitHub

Manage repositories, issues, pull requests, and workflows.

Next Steps