Model Context Protocol (MCP)

Model Context Protocol, MCP, defines how an agent discovers what tools a server offers and calls them, over a standard interface rather than a bespoke integration written for every tool. A server advertises its tools with a name, a description and an input schema; an agent asks what is available, then calls whichever tool the task requires, using the schema to know what to send.

An enterprise that already runs internal tool servers, a case lookup service, an internal search index, can expose them to an agent once, over MCP, instead of writing a custom connector for every agent that needs them, and can control exactly which tools are visible to which agent.

An internal MCP server exposing a case lookup tool is connected once and then reused by any agent in the organization that needs to look up a case.

In Dynamiq, an MCP Server tool connects an agent to a remote MCP server over the current standard transport or the legacy one, discovers its tools at run time, and expands each into a typed agent tool automatically. Include and exclude lists control exactly which tools an agent can see, alongside a built-in catalog of 2,100+ app integrations.