Glossary

What is Model Context Protocol (MCP)?

Last updated: 2026-05-05

Definition

Model Context Protocol (MCP) is an open standard introduced by Anthropic in 2024 that defines how AI agents connect to external data sources and tools. MCP servers expose data and capabilities; MCP clients (LLMs and agent platforms) discover and call them through a uniform interface — eliminating per-tool custom integration code.

Why Model Context Protocol matters

Before MCP, each AI agent platform built its own connector for every tool: a Slack integration here, a Gmail integration there, a custom internal-API connector. MCP standardizes the contract. Any MCP-compatible client can talk to any MCP server, the way any HTTP client can talk to any REST API. As of 2026, all major LLM vendors (OpenAI, Anthropic, Google) support MCP, and the registry of public MCP servers covers hundreds of tools.

How Model Context Protocol works

  1. 1A tool author publishes an MCP server: a small program that describes its capabilities (resources, tools, prompts) using the MCP schema.
  2. 2An AI agent platform (the MCP client) connects to the server over stdio, HTTP, or WebSocket.
  3. 3The client asks the server "what can you do?" and receives a manifest of tools, data resources, and prompt templates.
  4. 4When the LLM needs to use the tool, the agent platform calls the MCP server with structured arguments and receives a structured result.
  5. 5The result is fed back into the LLM context, so the model can use it in its next decision.
  6. 6Authentication, sandboxing, and rate limiting are handled at the MCP server boundary.

Examples

  • A GitHub MCP server: list repos, read files, create issues, comment on pull requests — without the agent platform writing any GitHub-specific code.
  • A SQL-database MCP server: list tables, query data, return rows — read-only by configuration.
  • A filesystem MCP server: read and write files in a sandboxed directory, useful for code-generation agents.

References

FAQ

Model Context Protocol — common questions

What is the difference between MCP and a regular API?
A regular API is purpose-built: each AI integration writes custom code for it. MCP is a self-describing protocol: the server tells clients what it can do via a standard schema, so any MCP-compatible client can use it without custom code. MCP sits one level higher than HTTP/REST.
Does AgentWorks support MCP?
Yes. AgentWorks agents can discover and call MCP servers as a first-class tool type, alongside built-in integrations. This means any tool that exposes an MCP interface — GitHub, Postgres, Slack, custom internal services — can be plugged into an AgentWorks agent without writing connector code.
Is MCP secure for production use?
MCP itself is a transport protocol; security is enforced at the server boundary. Best practices: run MCP servers in sandboxed environments, scope permissions per agent, audit every call, and prefer read-only servers where possible. AgentWorks logs every MCP call and supports approval gates on high-risk calls.
Do I need MCP if I already have integrations?
Not strictly. Native integrations remain useful for deep platform-specific behaviour. MCP shines for the long tail: internal tools, niche SaaS, custom services. Adding MCP support means the agent platform can grow without a connector backlog.