What are MCP servers? The Model Context Protocol explained with examples

MCP is an open standard for connecting AI apps to tools and data. What MCP servers are, a simple example, the spec, Supabase and n8n MCP, and the main risks.

Presenting to a room
Presenting to a room

Key takeaways

  • MCP, the Model Context Protocol, is an open standard for connecting AI applications to tools, data and prompts.
  • An MCP server exposes tools and resources; an MCP client inside an AI app, such as Claude or an IDE agent, discovers and calls them.
  • You can write a small MCP server in Python or TypeScript in minutes with the official SDKs.
  • Supabase and n8n both support MCP, so AI agents can query databases or trigger workflows.
  • Treat MCP servers like any integration with real permissions: least privilege, trusted sources and prompt-injection awareness.

MCP, the Model Context Protocol, is an open standard, introduced by Anthropic in late 2024, for connecting AI applications to external tools and data in a consistent way. An MCP server is a small program that exposes capabilities, such as "search the database" or "create a ticket", and any MCP-compatible client, such as Claude, coding agents or IDEs, can discover and use them. This page explains the meaning of MCP, servers in plain words, a working example, where the specification lives, real usage, Supabase and n8n support, and the common criticisms.

What does MCP mean?

In AI, MCP stands for Model Context Protocol: a standard way for AI applications to connect to tools, data sources and reusable prompts, so each integration is built once and works with many assistants.

Also asked as: what is meant by mcp

Before MCP, every AI app needed custom code for every tool, which led to many incompatible plugins. MCP defines a common protocol, similar in spirit to how USB standardised device connections, so a server written for one MCP client works with others. It is open source, with official SDKs in several languages, and it has been adopted widely by AI assistants, coding tools and platforms. In other contexts, MCP can mean other things, but in AI engineering it almost always means this.

What are MCP servers?

An MCP server is a program that exposes capabilities to AI applications through the Model Context Protocol: tools the model can call, resources such as files or records it can read, and prompts it can use. The AI app runs an MCP client that connects to the server.

Servers can run locally, communicating over standard input and output, or remotely over HTTP. Examples include servers for file systems, GitHub, databases, browsers, search engines and business apps. When a user asks a question, the AI model sees the list of available tools with their descriptions, decides to call one, and the client sends the request to the server, which does the work and returns results. The model then uses those results in its answer.

What are MCP servers, explained simply?

Think of an MCP server as a universal adapter between an AI assistant and a tool. The assistant asks the adapter "what can you do?", gets a menu of actions with instructions, and then asks it to perform one when needed.

Also asked as: what are mcp servers? explained · mcp servers explained simply

An everyday analogy: a phone's charging port. Before standard ports, every phone needed its own charger. With a standard port, any charger works with any phone. MCP plays that role for AI tools: build one MCP server for your college timetable, and Claude, a coding agent or any other MCP client can use it, without writing separate plugins for each. The important caveat is that a connected tool can take real actions, so you only connect servers you trust.

What is an example of an MCP server?

Here is a minimal MCP server in Python using the official SDK's FastMCP helper, exposing one tool that an AI assistant can call.

Also asked as: mcp server explained with example · mcp server explained reddit

# pip install "mcp[cli]"
from mcp.server.fastmcp import FastMCP

mcp = FastMCP("timetable")

@mcp.tool()
def next_class(course: str) -> str:
    """Return the next scheduled class for a course code, such as BCA301."""
    schedule = {"BCA301": "Operating Systems, Monday 10:00, Room 4"}
    return schedule.get(course.upper(), "No upcoming class found.")

if __name__ == "__main__":
    mcp.run()

Register this server in an MCP client's configuration, and the assistant can answer "when is my next BCA301 class?" by calling next_class. Real servers query databases or APIs instead of a dictionary, and validate inputs carefully.

Where can I find the MCP specification?

The official specification is published on the Model Context Protocol website, modelcontextprotocol.io, under the specification section, with versioned releases. The SDKs and reference servers are on GitHub under the modelcontextprotocol organisation.

Also asked as: where can i find specification for mcp servers

The specification defines the message format, based on JSON-RPC, the lifecycle of a connection, transports such as standard input and output and HTTP, and the primitives: tools, resources and prompts, plus client features such as sampling. It also covers authorisation for remote servers. Read the version your client supports, because the protocol has evolved since launch, and check each SDK's documentation for how features map to code.

Do developers use MCP servers in their workflow?

Yes. Developers commonly connect coding agents and AI assistants to MCP servers for GitHub, databases, documentation search, browsers, issue trackers and cloud consoles, so the assistant can read real context and take actions instead of guessing.

Also asked as: does anyone use mcp servers in their dev workflow

Typical uses: an agent that reads a GitHub issue, queries the development database, and opens a pull request; an assistant that searches internal documentation; or a browser server that lets an agent test a web app. The productivity gain comes from giving the model accurate context. The discipline that matters is scope: connect only the servers a task needs, use read-only access where possible, and review actions before they affect shared systems.

What is Supabase MCP?

Supabase provides an MCP server that lets AI assistants work with your Supabase projects: inspect database schemas, run SQL queries, manage tables and migrations, and fetch project information, within the permissions you grant.

It is useful during development: ask a coding agent to design a table, write a migration or debug a query, and it can check the real schema rather than inventing one. Because it can change your database, use it with development projects, prefer read-only mode where available, and never connect it to production data without careful permission settings. Supabase's documentation describes current setup steps and options for different MCP clients.

Does n8n have an MCP server?

Yes. n8n supports MCP in both directions: an MCP Server Trigger lets you expose n8n workflows as tools to MCP clients, and an MCP client tool lets n8n's AI Agent use tools from external MCP servers.

This means an assistant such as Claude can trigger your n8n automations, for example "create a lead in the CRM and send a welcome email", through MCP, while n8n handles the integrations. In the other direction, an n8n agent can call tools from other MCP servers. Node names and options evolve, so check n8n's documentation for the current MCP nodes in your version.

How do I use MCP with n8n?

To expose a workflow to AI assistants, start a workflow with n8n's MCP Server Trigger, add tool nodes for the actions you want, publish it, and add the server's URL to your MCP client's configuration with authentication.

Also asked as: how to n8n mcp

Steps:

  • Create a workflow with the MCP Server Trigger node.
  • Attach tools, such as a Google Sheets lookup or an HTTP request, with clear names and descriptions.
  • Enable authentication on the trigger.
  • Publish the workflow and copy its production URL.
  • Add the URL to your MCP client and test with a simple request.

To consume external MCP servers inside n8n, add the MCP client tool to an AI Agent node and point it at the server.

What are common criticisms of MCP servers?

Developers mainly raise security and quality concerns: servers can expose powerful actions, malicious or poorly written servers can steal data, prompt injection through tool results can mislead agents, and connecting too many tools fills the model's context and confuses tool choice.

Practical safeguards:

  • Install servers only from trusted sources and review their code or permissions.
  • Grant least privilege: read-only database users, scoped API tokens.
  • Treat tool outputs and fetched content as untrusted data, never as instructions.
  • Connect only the servers needed for a task.
  • Require confirmation for destructive actions and keep logs.

These are the same principles as any integration with real permissions; MCP makes integration easier, so discipline matters more.

Sources

  1. Model Context Protocol, documentationmodelcontextprotocol.io
  2. Model Context Protocol, specificationmodelcontextprotocol.io
  3. Model Context Protocol, Python SDKgithub.com
  4. Supabase, documentationsupabase.com
  5. n8n, Documentationdocs.n8n.io
Pranjul Rathour
Pranjul Rathour
GenAI Engineer · India

GenAI engineer and AI product builder with 2+ years shipping production-grade AI systems: RAG pipelines, fine-tuned LLMs, hybrid retrieval and multi-modal apps across vision, speech and OCR, architected end to end from ingestion to deployment. Leads engineering for SCULT INDIA's 14-member team, founded the 500+ member TechVerse Enclave community and has mentored 200+ students. Three hackathon first prizes: Changethon 2025 (IIT Roorkee), Product Genesis at Vividhotsava 2025 (CSJMU) and BYTEBATTLE (MeetKats).

Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges. For campus sessions the inviting institution covers the visit end to end: travel (a First AC train ticket for journeys up to five hours, a flight for anything longer), accommodation, meals, and pickup and drop; the honorarium and workshop fees are negotiable on WhatsApp or on the call, and requests are welcome from institutions that can cover the visit this way. Email pranjulrathour41@gmail.com.

Keep reading

More on Shipping AI apps

All Shipping AI apps guides →
Campus talks · hackathon judging · mentoring

Want this as a live session at your college?

Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges. For campus sessions the inviting institution covers the visit end to end: travel (a First AC train ticket for journeys up to five hours, a flight for anything longer), accommodation, meals, and pickup and drop; the honorarium and workshop fees are negotiable on WhatsApp or on the call, and requests are welcome from institutions that can cover the visit this way.

Pranjul Rathour, GenAI engineer in India