MCP: Model Context Protocol - Quickstart

Set up your first MCP server in Claude Code in under 5 minutes. This guide shows you how to add an MCP server via stdio or SSE, test the available tools, and secure your connections - step by step, with no unnecessary theory.

Adding an MCP server (stdio, SSE, HTTP) in 5 minutes is an essential aspect of mastering Claude Code.

MCP (Model Context Protocol) is an open standard created by Anthropic that allows Claude Code to connect to external tools - databases, browsers, APIs - via a unified protocol. MCP supports three transport modes: stdio, SSE, and Streamable HTTP. over 50 community MCP servers are available, covering use cases ranging from web search to browser automation.

What are the prerequisites to get started with MCP?

Before launching your first MCP server, verify these four points. If you have already installed Claude Code, you are almost ready.

• Node.js 22 or higher installed (node -v)
• Claude Code v1.0.33 or higher (claude --version)
• npx available in your terminal (npx --version)
• A GitHub account with a personal token (for the GitHub MCP server)

In practice, 90% of MCP errors stem from a Node.js version below 18. Run node -v before anything else.

Key takeaway: four tools are enough - Node.js 22, an up-to-date Claude Code, npx, and a GitHub token.

How to add a stdio MCP server in 2 minutes?

The stdio transport is MCP's default mode. The server runs as a child process of Claude Code, which simplifies configuration. To understand the protocol fundamentals, check the complete MCP guide which details each concept.

Run this command to add the GitHub MCP server:

claude mcp add github -- npx -y @modelcontextprotocol/server-github

Claude Code registers the server in your .claude.json file. Verify that the server is properly listed:

claude mcp list

You should see a line github: connected (stdio). In practice, this command takes less than 10 seconds to execute.

To add the Brave Search server, the syntax is identical:

claude mcp add brave-search -- npx -y @anthropic/mcp-server-brave-search

the stdio mode offers an average latency of 12 ms per tool call, compared to 45 ms for SSE.

Key takeaway: a single claude mcp add command is enough to connect a stdio server.

How to configure an MCP server in SSE or HTTP mode?

The SSE (Server-Sent Events) transport allows connecting Claude Code to a remote MCP server. Use the --transport sse option to specify this mode. If you are new to Claude Code, the first conversations guide will help you understand tool interaction.

claude mcp add my-remote-server --transport sse https://mcp.example.com/sse

For the Streamable HTTP transport, available since MCP v2025-03:

claude mcp add my-http-server --transport http https://mcp.example.com/mcp

In practice, the stdio mode covers 80% of needs. Reserve SSE and HTTP for servers hosted on a remote machine or in the cloud.

Here is how to verify the connection to a remote server:

claude mcp list --json | grep "my-remote-server"

Key takeaway: stdio for local, SSE for remote, HTTP for cloud APIs with OAuth.

How to use MCP tools in a Claude Code session?

Once your servers are added, Claude Code automatically detects the available tools. Start a session and ask Claude to use an MCP tool. The essential slash commands let you manage your servers directly in session.

claude
# In session, type:
> List the open issues of the anthropics/claude-code repo using the GitHub tool

Claude Code displays a permission request before each MCP call. Accept with y or configure auto-approval via permissions and security.

To see all available MCP tools in session, use the /mcp slash command:

> /mcp

This command displays the list of connected servers, their status, and exposed tools. On average, the GitHub server exposes 15 distinct tools (issues, PRs, files, branches). You can also check the conversation examples to see concrete MCP use cases.

Key takeaway: Claude Code detects MCP tools automatically - ask in natural language what you want to do.

How to configure and secure MCP in 5 minutes?

MCP security relies on three mechanisms: environment variables for tokens, Claude Code permissions, and configuration scope. Configure your tokens via environment variables to avoid exposing them in configuration files. For more details, the MCP tips cover best practices.

export GITHUB_TOKEN="ghp_your_token_here"
claude mcp add github -e GITHUB_TOKEN -- npx -y @modelcontextprotocol/server-github

The -e option passes the environment variable to the MCP process without writing it to .claude.json. In practice, 100% of MCP servers requiring authentication support environment variables.

To limit a server's scope to the current project, add the --scope project flag:

claude mcp add github --scope project -e GITHUB_TOKEN -- npx -y @modelcontextprotocol/server-github

In practice, the project scope is recommended for repository-specific servers. The user scope is suitable for universal servers like Brave Search.

To dive deeper into the Claude Code permissions model, check the permissions and security guide which covers auto-approval rules.

Key takeaway: use -e for tokens, --scope project to isolate servers per project.

What are the most popular MCP servers in 2026?

Here are the five most popular MCP servers used by the community. Each can be installed with a single command. these servers collectively account for over 500,000 monthly downloads.

The Playwright server can capture screenshots, navigate pages, and extract content - on average a capture takes 2.3 seconds. The GitHub server covers 95% of common repository operations.

To discover other servers and their advanced configurations, explore the MCP FAQ which answers the most frequent questions. You can also check the slash command examples to speed up your MCP workflow.

Key takeaway: GitHub, Brave Search, and Playwright cover 80% of common MCP tool needs.

How to verify that everything works correctly?

Run this complete verification sequence in under 30 seconds. This test validates that your servers are connected, tools are accessible, and authentication works.

# 1. Check registered servers
claude mcp list

# 2. Launch Claude Code and test a tool
claude
> Use the GitHub tool to list my repos

If you see a spawn npx ENOENT error, your PATH does not contain npx. Fix with export PATH="$PATH:$(npm bin -g)". If a server shows disconnected, restart Claude Code - restarting automatically reconnects all servers.

The average startup time for a stdio server is 1.2 seconds. A remote SSE server connects in 3 to 5 seconds depending on network latency. To diagnose common issues, the installation tutorial includes a comprehensive troubleshooting section.

Key takeaway: claude mcp list is your primary diagnostic command - use it at the slightest doubt.

How to go further with MCP and Claude Code?

MCP opens up extensive possibilities: chaining multiple servers, creating your own custom servers, and integrating CI/CD workflows. SFEIR Institute offers structured training to master these tools in real-world conditions.

To deepen your understanding of MCP and Claude Code, the one-day Claude Code training guides you through hands-on labs covering installation, MCP configuration, and advanced tool usage. You will leave with a fully operational augmented development environment.

If you want to integrate Claude Code into a complete development workflow, the two-day AI-Augmented Developer training covers assisted pair programming, test generation, and code review automation. For experienced developers, the one-day advanced training explores custom MCP server creation and multi-agent orchestration.

Here is how to continue your learning:

1. Explore the complete MCP guide to understand the protocol architecture
2. Practice with conversation examples integrating MCP tools
3. Secure your configuration with the permissions guide
4. Create your own MCP server by following the official specification on modelcontextprotocol.io

Key takeaway: MCP is an expanding ecosystem - start with the popular servers, then create your own based on your needs.