What is MCP? A plain-language guide for people who are not developers
If you use AI agents, you have probably seen the letters MCP in settings, tutorials and product pages. It sounds technical, but the idea is simple, and knowing it helps you decide what to connect your agent to.
The short version
MCP, the Model Context Protocol, is a common language between AI agents and outside services. The service runs an MCP server; your agent connects to it as a client. The server tells the agent which tools it offers — for example "create a site" or "publish files" — and the agent calls them when your request needs them.
A popular comparison is USB-C. Before it, every device had its own plug. Before MCP, every AI app needed a separate integration with every service. Now a service builds one MCP server, and any agent that speaks MCP can use it.
Who supports it
Anthropic introduced MCP as an open standard in November 2024. OpenAI, Google, Microsoft and many others have since adopted it. Claude Code, Codex, Cursor and most other coding agents can connect to MCP servers.
What it looks like in practice
Take aiput.site. When your agent connects, it asks the server for its tools and gets a list: create_site, deploy_site, rollback_site and a few more. Each tool comes with a description of what it does and what its rules are — for example, that a site needs an index.html at the top.
Then you say "publish this website". The agent picks create_site, then deploy_site with your files, and gets back the site's address. You never see the protocol. You talk to the agent; the agent talks to the server.
Local and remote servers
Some MCP servers run on your own computer — to read files, say, or to control a browser. Others run on the internet and are reached over HTTP, like aiput.site at https://aiput.site/mcp. Remote servers usually need a key or a sign-in, so the service knows whose account the agent is acting for.
What a connected agent can and cannot do
This is the part that matters for safety: an agent can do exactly what the server's tools allow, and nothing more. aiput.site's tools manage your sites — create, publish, roll back, rename, delete. There is no tool for payments, account settings or email, so an agent connected to aiput.site cannot touch them.
A few rules of thumb:
- connect only servers from services you trust;
- treat the key like a password: it lets anyone use the same tools;
- read what the agent is about to do before you confirm, especially when it wants to delete something.
Do I need to understand MCP to use it?
No. With aiput.site you copy one message from your dashboard into the chat with your agent, and the agent sets itself up. See how to connect your agent and how aiput.site works.