← Back to Lessons
Getting Started

Connect Claude to Your Tools with MCP

MCP lets Claude Code reach into your other tools, like Notion, GitHub, or a database, and act on them directly instead of you copying and pasting. Here is the beginner version.
⏱ About 10 minutes

What MCP is. MCP, the Model Context Protocol, is an open standard that connects Claude Code to outside tools, data, and APIs. Once you connect a tool, Claude can read from it and act on it directly. The signal that you want one: you keep copying data out of some other app and pasting it into Claude.

Plain example. Connect the GitHub server and Claude can read a pull request and comment on it. Connect a database server and it can answer "how many orders shipped last week" by querying it, instead of you exporting a spreadsheet.

1
Find a server

Browse reviewed connectors in the Anthropic Directory, then add any of them.

Open the Anthropic Directory →

Popular beginner-friendly ones include Notion, GitHub, Sentry, and database connectors. Each has a name and either a URL (for cloud tools) or a small command (for local ones).

Only connect tools you trust

A server you connect can feed content into Claude, which carries a prompt-injection risk. Stick to official or well-reviewed servers, and do not connect something you do not recognize.

2
Add a cloud server (no account needed)

Cloud servers are added with claude mcp add --transport http, giving the server a name and a URL. A great one to start with needs no account and no API key: DeepWiki, a free server that can read and answer questions about any public GitHub repository.

claude mcp add --transport http deepwiki https://mcp.deepwiki.com/mcp

That is the whole setup. Now ask Claude about any repo and it reads the docs through the server for you:

Use DeepWiki to explain what the microsoft/playwright repository does and how to get started with it.
Some servers do need a sign-in

DeepWiki is open to everyone. Many other cloud servers (GitHub, Slack, your database) ask you to log in or paste a token, since they touch your private data. For those, run /mcp inside Claude Code after adding the server and follow the browser sign-in. Your tokens are stored securely.

3
Add a local tool (stdio server)

Some servers run as a small program on your machine. These use -- to separate the name from the command. A favorite is the Playwright server, which lets Claude drive a real web browser. It needs Node.js 18 or later (check with node --version):

claude mcp add playwright -- npx -y @playwright/mcp@latest

The part after -- is the command that starts the server. Now Claude can open and click around a browser for you. Try it:

Use Playwright to open https://demo.playwright.dev/todomvc, add three to-do items called "buy coffee", "walk the dog", and "ship the project", then tell me the final list.

A real browser window opens and you watch Claude work. Local servers like this are great for tools that need direct access to your machine.

4
Manage your servers

A handful of commands cover the day to day:

claude mcp list
claude mcp get deepwiki
claude mcp remove deepwiki

And inside a Claude Code session, check connection status, sign in, or reconnect:

/mcp
Use the tools

Once a server is connected, you do not call it specially. Just ask in plain language: "Ask DeepWiki how routing works in the vercel/next.js repo" or "Use Playwright to open my localhost site and check the homepage." Claude picks the right tool.

5
Where a server applies: scopes

When you add a server, you can choose where it is available with --scope.

local (default)

Available only to you, only in the current project. Good for personal or experimental connections.

project

Saved to a .mcp.json file in the project so your whole team gets the same tools when they pull the repo. Add it with --scope project.

user

Available to you across every project on your machine. Add it with --scope user. Good for tools you use everywhere.

claude mcp add --transport http deepwiki --scope user https://mcp.deepwiki.com/mcp

Questions?

Made by AI Service Engine · official MCP docs · browse connectors