Model Context Protocol (MCP)
The Model Context Protocol (MCP) is an open standard that lets an AI assistant connect to external tools and data sources, such as a database or a calendar, through one consistent interface instead of a separate custom integration for every system it needs to reach.
Submit a project Plan an MCP server integrationReviewed by David Nguyen (CEO) · Updated 6 Oct 2026 · 3 min read
This term is one of the entries in the OutsourcingVN glossary of words buyers meet while scoping an AI agent project.
Why it matters
Before a shared protocol, every connection between an AI assistant and a business system was its own one-off integration, rebuilt whenever the assistant or the system changed. MCP standardises that connection: a system exposes a defined set of tools and data through an MCP server, and any MCP-compatible assistant can call them the same way. OutsourcingVN is operated by Netbase JSC, and buyers asking for an AI agent that can "do things" in their existing systems, not just answer questions about them, are usually describing an MCP integration.
An example in practice
A support team wants its AI assistant to look up an order status and issue a refund inside policy limits, not just describe how refunds work. An MCP server is built in front of the order system, exposing a narrow set of callable actions — look up an order, issue a refund under an agreed limit — with authentication and logging on each call. The assistant calls the server; it never gets a direct database connection.
Common misreadings
MCP is not a model and does not make a model smarter on its own — it is a connection standard that gives an already-capable model something new to call. It is also not a bypass of normal access control: a well-built MCP server exposes a fixed, narrow set of actions and still enforces authentication and scopes, rather than handing the model a general-purpose system login. And adopting MCP does not remove the need to decide which actions an agent may take unsupervised and which need a person to confirm first — that is a design decision the protocol does not make for you.
Plan the next step for your project
Common questions
It works with any assistant or client built to support the protocol; adoption is broad but not universal.
No — a well-built server exposes a fixed, narrow set of tools and resources, not a general connection to the underlying system.
Related decisions
Planning the tools and resources an MCP server exposes, its authentication and logging, and how it is versioned and tested, is covered in the MCP server integration guide. When you have a system you want an agent to call safely, describe the actions it needs and the limits around them, and Netbase will respond through Netbase's own outsourcing-services platform; submit a project when you are ready.