Reference for Enterprise MCP — published MCP tools, enterprise capability keys, and multi-datasource selection after integration upload.
Source of truth
| Source | Path / command |
|---|---|
| Published MCP surface | Dataplane after aifabrix upload <systemKey> |
| Datasource exposure | exposed block in the external-datasource schema |
| Live tool list | aifabrix show <systemKey> --online |
| Concept narrative | Enterprise MCP (pillar) |
| Builder certification | Certification |
Dataplane knowledgebase articles describe datasource selector behavior and capability metadata — verify against your deployed version when debugging tool lists.
Concepts
| Concept | Meaning |
|---|---|
| Enterprise capability key | Deduplicated business action id (e.g. customer.list, deal.reviewPipeline) |
| MCP tool | One tool per enterprise capability key on published MCP surfaces |
| Datasource selector | When multiple child datasources share a resourceType, callers pass datasource to choose execution target |
| Exposure | Controlled by datasource exposed config and upload/compile pipeline |
| Business metadata | Tool inputs/outputs use field mappings — not raw vendor field names |
MCP never exposes raw vendor URLs, API keys, or unconstrained REST paths to AI clients.
Publish and verify
aifabrix repair <systemKey> --expose
aifabrix validate <systemKey>
aifabrix upload <systemKey> --probe
aifabrix upload <systemKey>
aifabrix show <systemKey> --online
Then test execution:
aifabrix test-e2e <systemKey>
aifabrix datasource test-e2e <datasourceKey> --app <systemKey>
Multi-datasource selector
When Enterprise MCP combines two or more child datasources for the same resourceType and capability, request schemas include a first-level datasource input so callers explicitly choose the child to execute.
Integrators document which datasource keys apply for each resource type in field mappings and capability design — see Governed capabilities.
OpenAPI REST parity
REST routes published alongside MCP use the same compiled enterprise capability keys. Application clients and MCP clients share governance and certification scope.
Limits
Published MCP tool names and selector behavior depend on your uploaded integration set and dataplane version. Always verify with show --online after upload — do not assume local JSON matches published tools.