What Is an MCP Server? MCP Explained for Non-Developers

An MCP server is a small program that lets an AI app like Claude use another tool on your behalf: search your Google Drive, read a Notion page, draft a Gmail reply or export a Canva design. MCP stands for Model Context Protocol, the open standard that defines how AI apps and tools talk to each other, so a tool maker builds one server and it works in any app that supports MCP. You connect a server once, sign in, and from then on Claude can use that tool's actions whenever your request needs them.

MCP in plain English

The official MCP documentation sums it up with a hardware analogy: "Think of MCP like a USB-C port for AI applications" (modelcontextprotocol.io). Before one standard plug existed, every device needed its own cable, and before MCP every AI app needed a custom integration for every tool.

A protocol is simply an agreed set of rules for how two programs exchange information. In MCP, three roles share the work:

A server can offer three kinds of things to the app:

Tools are what you will notice day to day. Here is what happens behind a single request:

Why MCP matters if you don't code

• You stop copying and pasting. Without a connection, getting CRM data into an AI chat means exporting, downloading and uploading. With one, you ask in a sentence.
• One standard means less work for everyone. A tool maker builds one server instead of a separate integration for every AI app.
• Claude can act, not only answer. A server with write tools lets Claude create the draft or update the record, which is the main benefit and the main risk.

Anthropic introduced MCP in November 2024. In December 2025 it donated MCP to the Agentic AI Foundation, a fund under the Linux Foundation, so no single company controls the standard.

Local and remote servers

Servers come in two kinds, and the difference decides how you install them.

In the Claude web and desktop apps, connections to remote servers come from Anthropic's cloud rather than from your computer.

Connectors, extensions and servers are the same idea

Each Claude product uses its own word for the same thing:

Anthropic's directory marks many connectors "Anthropic verified", and the ai school MCP directory lists more servers worth a look.

How to connect an MCP server in Claude Code

The steps follow the Claude Code MCP documentation:

1. Find the official address. Take it from the tool maker's own documentation.
2. Add the server. Run the command below in your terminal; this one adds Notion's hosted server.
3. Sign in. Start Claude Code with claude, type /mcp, select the server and follow the browser login. This is OAuth, the "Sign in with..." flow that gives Claude a revocable key instead of your password.
4. Test it read-only. Ask for something that only reads, like the prompt below.

$ claude mcp add --transport http notion https://mcp.notion.com/mcp
$ 

Search my Notion workspace for the onboarding checklist and summarize it in five bullets. Don't change anything.

A local server is added with a command that starts the program. This one adds Microsoft's Playwright server, which lets Claude open web pages and click through them in a browser, and it needs Node.js installed:

$ claude mcp add playwright npx @playwright/mcp@latest
$ 

The --scope setting decides who can use a server:

Because a project's .mcp.json file may have come from someone else, Claude Code asks for your approval before it uses the servers listed there. To review or tidy your servers, run these in the terminal, or type /mcp inside a session:

$ claude mcp list
$ claude mcp get notion
$ claude mcp remove notion
$ 

How to connect one in the Claude app

These steps follow Anthropic's help article on custom connectors and work in the browser and the desktop app.

From the directory

1. Open the directory. Go to Customize > Connectors and browse.
2. Connect a tool. Pick a connector, such as Google Drive, and sign in to that service.
3. Switch it on in a chat. Click the + button at the bottom left, choose Connectors, and turn the connector on for that conversation.

Any remote server by address

1. Start a custom connector. In Customize > Connectors, click + Add, then Add custom connector.
2. Enter the details. Type a name and the server's address, then click Continue.
3. Choose how to sign in. Pick sign in now, sign in when needed, or no sign in, then click Add.

Free plans are limited to one custom connector. On Team and Enterprise plans, owners add connectors for the organization, and members then connect their own accounts.

Local servers in Claude Desktop

Claude Desktop installs local servers as extensions: open Settings > Extensions, click Browse extensions, and install one. To install a .mcpb file someone gave you, open Advanced settings on the same page and choose Install Extension.

The older manual method still works when a server's docs ask for it. Following the MCP guide to local servers, open Settings > Developer > Edit Config from the Claude menu, add the server to the config file, then quit and restart the app.

Local servers set up this way work only in the desktop app, not on claude.ai.

Safety checklist before you connect a server

10 MCP servers worth connecting

These are official servers made by the companies behind each tool, chosen for people who don't code. The last column shows the quickest route.

If a tool you rely on has no server of its own, Zapier offers an MCP server that lets Claude run actions in the apps connected to your Zapier account. For more options, see the ai school MCP directory.

When you don't need an MCP server

• The files are already on your computer. Claude Code reads and edits local files directly, with no server needed.
• The job is a fixed, always-on pipeline. "Every new form lead goes into a sheet and gets an email" belongs on an automation platform; see the n8n tutorial for beginners, or how to automate invoices with AI for an example that mixes both approaches.
• You want a procedure, not a new tool. That is a skill, covered in how to create a Claude skill.

What to do next

Connect one read-only server today, such as Google Drive or Notion, and ask it three questions you would normally answer by searching by hand. Once the answers prove useful, add one write action you control, like drafting rather than sending.

Keep the vetting habit from the checklist for every new server, and use the MCP directory to find the ones that match your tools. If you would rather set up MCP, skills and CLAUDE.md with a guide at your side, the Claude Code course walks through all three.