THE DEFINITIVE GUIDE

Model Context
Protocol

The open standard for connecting AI assistants to the tools, data, and systems they need. Learn MCP with interactive tutorials and a complete server directory.

WITHOUT MCP

Every AI × every tool = custom integration

5 AI assistants
× 20 tools
= 100 custom integrations

WITH MCP

One protocol connects everything

5 AI assistants
+ 20 MCP servers
= 25 components total
UNDERSTANDING MCP

What, Why, and How

WHAT

A Universal Protocol

MCP lets AI models interact with external tools, databases, and APIs through a standardized protocol. Think of it as USB-C for AI integrations -- one connector that works everywhere, replacing dozens of custom adapters.

WHY

One Protocol, Every Tool

Before MCP, every AI assistant needed custom code for every tool. Now there is one protocol to connect any AI assistant to any tool. No more bespoke integrations per model. Build once, connect everywhere.

HOW

Servers, Clients, Resources

MCP servers expose tools, resources, and prompts. Clients like Claude Desktop and Cursor connect to servers and use them. The protocol handles capability negotiation, request routing, and data serialization automatically.

ARCHITECTURE

How MCP Works


  +--------------------------------------------------+
  |              CLIENT APPLICATION                   |
  |    Claude Desktop  /  Cursor  /  Your App         |
  +--------------------------------------------------+
                        |
                        |  MCP Protocol (JSON-RPC 2.0)
                        |  stdio / SSE transport
                        |
  +--------------------------------------------------+
  |               MCP SERVER                          |
  |    Exposes: Tools / Resources / Prompts           |
  +--------------------------------------------------+
                        |
                        |  Native APIs & SDKs
                        |
  +--------------------------------------------------+
  |           EXTERNAL SYSTEMS                        |
  |    Databases / APIs / File Systems / Services     |
  +--------------------------------------------------+

TOOLS

Functions the AI can call. Like "search_files", "run_query", or "send_message". The server defines the schema, the client invokes them.

RESOURCES

Data the AI can read. Like file contents, database records, or API responses. Resources are identified by URIs and can be subscribed to for updates.

PROMPTS

Pre-built prompt templates the server provides. Users can select them from the client UI. Prompts can include dynamic arguments and embedded resources.

SERVER DIRECTORY

Browse by Category

Explore MCP servers across every category. From databases to browser automation, find the right server for your use case.

QUICK START

Get Running in 3 Steps

01

Install a Client

Download Claude Desktop, Cursor, or any MCP-compatible client. These applications know how to connect to and communicate with MCP servers.

02

Add an MCP Server

Edit your client configuration file to add an MCP server. For Claude Desktop, this means adding an entry to claude_desktop_config.json.

03

Use Tools in Conversation

Start a conversation and the AI can now use the tools exposed by your MCP server. Ask it to read files, query databases, or call APIs naturally.

EXAMPLE: claude_desktop_config.json

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/you/Documents"
      ]
    }
  }
}