MCP is the baseline, not the extra
Anthropic's Model Context Protocol is first-class. MCP tools, resources, and prompts are recognized natively — no custom glue, no per-integration exceptions.
MCP gives every agent a standard way to talk to tools and data. Treating it as the baseline means any MCP-compliant tool in the ecosystem plugs in — your vendors, your open-source favorites, your internal services — without adapters.
What native MCP means
- 01
Automatic discovery
Point at an MCP server; the platform reads its manifest and makes tools available to agents immediately.
- 02
Typed bindings
MCP schemas produce typed stubs agents can reason about, not opaque function calls.
- 03
Governed exposure
Tools from external MCP servers inherit your policy, audit, and access model — as if they were internal.
Capabilities
Bidirectional
You can both consume external MCP servers and expose internal capabilities as MCP for partners and vendors.
Versioned servers
MCP server versions are tracked; breaking changes surface before they break your agents.
Sandboxed tools
External tools run under the platform's guardrails, not unconstrained in your network.
Ecosystem leverage
The catalog of MCP tools grows daily — you inherit the ecosystem without building connectors yourself.