TECHNOLOGY //
Extensibility
2501 agents can call MCP servers as tools, public or in-house, given only to the agents that need them. When an MCP server helps, and when it only adds noise.

TICKETS FROM
ServiceNow or another ITSM
CATEGORY
Extensibility
AUTONOMY
Investigate only, with a person, or on its own
DEPLOYMENT
On-prem, cloud or hybrid
█
TECHNOLOGY_BRIEFING
// WHAT 2501 DOES
2501 agents can use MCP servers as tools: instead of composing command lines, the agent calls functions the server describes in plain language. A plugin can be a public MCP server or one you built in-house, and each is given only to the agents that need it.
An agent working through a complicated command-line tool makes the mistakes a person makes with one: the wrong argument, an option that does not exist. A well-described tool removes most of that.
Plugins are set up with 2501 for each customer so they work reliably with the agents. Each one is assigned to the agents that need it and no others, scoped to one organisation or to the whole tenant, and can be switched off at once if a function misbehaves. With VMware, for example, agents struggled with the command-line client and managed machines, snapshots and datastores without friction through an MCP-based plugin. Add an MCP server where agents consistently struggle with a tool, not for tools they already handle well: every plugin adds to the agent's context, and a crowded context makes a less reliable agent.

Can we connect our own MCP server? Yes. In-house MCP servers work as well as public ones.
Does every agent get every plugin? No. Plugins are assigned per agent.
Should we wrap every tool in an MCP server? No. Add one where agents struggle with a tool; otherwise it only adds context and cost.
> READY_TO_DEPLOY
Book a technical demo and walk through your own environment with the 2501 team.