What is an MCP server? A plain-English guide for non-developers
Aperisa ยท 4 min read
An MCP server is a small program that lets an AI assistant, such as Claude or ChatGPT, use something outside the chat: your calendar, a database, a folder of documents, a project tracker. MCP stands for Model Context Protocol, an open standard that defines how the assistant and the tool talk to each other. The assistant is the client. The MCP server is the connector on the other side.
If you've ever wished your AI assistant could just look something up instead of asking you to paste it in, that's the gap MCP fills.
Why does MCP exist?
AI assistants are good at reading and writing, but on their own they only know what's in the conversation. Before MCP, every company that wanted its product inside an assistant had to build a custom integration for each assistant separately. That meant a lot of one-off work and a lot of integrations that didn't exist.
Anthropic published MCP as an open standard in November 2024. The idea is the same one behind USB: agree on one plug shape, and any device works with any port. A service builds one MCP server, and any assistant that supports MCP can use it. Through 2025 the other major AI companies added support, so it has become the common way to connect assistants to outside tools.
How does an MCP server work?
There are three parts.
- The host. The app you're talking to, like Claude Desktop, ChatGPT or a coding tool.
- The client. A piece inside the host that knows how to speak MCP.
- The server. The connector for a specific service. It tells the assistant what it can do, and it does those things when asked.
When you connect a server, it announces a list of tools, each with a name and a short description. A calendar server might offer "list events" and "create event". When you ask a question, the assistant reads those descriptions, decides whether a tool would help, and calls it. The server does the work and sends the result back, and the assistant uses it in its answer.
You don't call the tools yourself. You ask in plain language, and the assistant chooses.
What can an MCP server give an assistant?
The standard has three kinds of things a server can offer.
- Tools are actions: search, look up, create, update.
- Resources are things to read: files, records, pages.
- Prompts are ready-made instructions for common tasks.
Most servers you'll meet are mostly tools.
Where do MCP servers run?
Either on your computer or on the internet.
A local server runs on your own machine and is usually started by the assistant app. It's common for developer tools and for anything that needs your local files.
A remote server runs on the service's side, and you connect by adding its URL and signing in. This is the kind most people will use, because there's nothing to install.
Is it safe to connect an MCP server?
An MCP server can do whatever its tools allow, with whatever account you signed in with. So the questions to ask are the same ones you'd ask about any app you give access to.
- Can it only read, or can it also change things? A server that can send email or delete files deserves more caution than one that can only search.
- Whose account does it use? If it signs in as you, it can see what you can see.
- Can you see what it accessed? A good service keeps a record of every read, and lets you look at it.
- Do you trust the content it reads? A document or web page can contain text written to trick an AI into doing something you didn't ask for. This is called prompt injection. It's a reason to be careful with servers that can both read untrusted content and take actions.
Most assistants also ask for your approval before calling a tool, at least the first time. Leave that switched on for anything that can change things.
What does this look like in practice?
Say you connect a server for your own documents and ask, "When does my lease renew?" Without MCP, the assistant would tell you to look it up, or worse, guess. With it, the assistant calls the server's search tool, gets the relevant passage, and answers from that.
Aperisa runs an MCP server for exactly this. It gives an assistant like Claude access to a structured, private record built from your Gmail, Drive and financial accounts, and each answer points to the document it came from. You can connect your own AI to it the same way you'd connect any other MCP server.
The short version
An MCP server is a connector. It lets an AI assistant use a tool or read data it couldn't reach before, using one shared standard instead of a custom integration for every app. Connect the ones you need, prefer read-only access where you can, and keep the approval prompts on.
Questions
What does MCP stand for?
Model Context Protocol. It is an open standard, introduced by Anthropic in November 2024, for connecting AI assistants to outside tools and data.
Do I need to be a developer to use an MCP server?
Not anymore. Many services now offer a connector you add by pasting a URL into Claude or ChatGPT and signing in. Running your own server locally still takes some technical comfort.
Is an MCP server safe?
It is as safe as the access you give it. Check whether it can only read or can also change things, what account it signs in as, and whether you can see a record of what it accessed.
What is the difference between an MCP server and a plugin?
A plugin usually works with one app. An MCP server follows a shared standard, so the same server can work with any assistant that supports MCP.
Published
Keep reading
- OpenClaw MCP setup: a remote server with a Bearer header
OpenClaw MCP setup for a remote server with a Bearer header: mcp.servers, not mcpServers or mcporter, an env-backed token, and 2026.6.5 or later.
- n8n MCP Client node: connect a remote MCP server, and fix a missing auth header
Set up the n8n MCP Client and MCP Client Tool nodes against a remote MCP server, and fix the missing Authorization header behind most 401s, step by step.
- Codex CLI and remote MCP servers: running unattended with a Bearer key
Connect Codex CLI 0.162 to a remote MCP server with a Bearer key in config.toml, then make codex exec call its tools unattended without turning off the sandbox.