Enterprise MCP is the governed AI interface to Enterprise Knowledge. It packages business concepts, relationships, searchable context, available capabilities, permissions, and evidence requirements — so AI works through business language instead of raw systems.
Why it matters
AI tools need a stable, governed surface to discover context and request work. Enterprise MCP exposes certified enterprise capabilities and context through the Model Context Protocol — mediated by Operational Trust, not direct credentials to underlying systems.
How it works
Enterprise MCP combines:
- business resource types and metadata
- cross-system relationships
- search and retrieval context
- governed capabilities exposed for the active role
- permission and evidence requirements
AI clients connect to Enterprise MCP to understand what exists and which business actions may be requested. Execution still flows through capability checks, certification, and evidence capture.
Enterprise MCP is ready when
Use this checklist after each integration (repeat per connected system when you add CRM, document store, or other sources):
- Expose — business capabilities are published from datasource configuration (Capabilities on the configure track)
- Upload — integrators publish manifest changes to the dataplane successfully
- Online — operators confirm compiled MCP tools and capability keys appear in the live catalog
- Certify — operations, agent metadata trust, and governance certification pass for the scope you need
- Relationships — cross-system links are uploaded if Role Assistants need combined context (Cross-system relationships)
- Role Assistants — administrators activate roles and users can activate assistants (From integrations to Role Assistant)
Enterprise MCP is the compiled surface after publish — not a separate product you install. If tools are missing, fix manifest, upload, and certification before expecting Role Assistants or external AI clients to call them.
Limits
Enterprise MCP tool catalogs depend on which systems are integrated, certified, and exposed in your environment. Not every capability or datasource appears in MCP until published through the integration lifecycle.
Example
An AI assistant uses Enterprise MCP to search customers, retrieve a governed customer overview, and request deal.reviewPipeline — each step scoped to the user's active role and certified datasources.
Business value
Enterprise MCP gives AI a business-language interface to the enterprise — without exposing raw APIs or bypassing governance.