Documentation Index

Fetch the complete documentation index at: https://docs.aifabrix.ai/llms.txt

Use this file to discover all available pages before exploring further.

Configure Enterprise MCP

  • Updated on Jun 29, 2026
  • Published on Jun 29, 2026
  • 1 minute(s) read
  • MR
  • EB
 Prev Next

Enterprise MCP is the published capability surface Role Assistants and MCP clients consume after upload — compiled from certified Business Entity manifests, not raw vendor APIs.

Prerequisites

  • Business Entities with exposed contracts and capabilities[] defined
  • Green validate and successful upload
  • OpenAPI and MCP contracts understood at a high level

Where it lives

Layer Role
Business Entity exposed, capabilities, execution.cip.operations — what may publish
Connected System generateMcpContract, certification block
Runtime Enterprise MCP tools after upload (same governed keys as REST)

This page is the configure outcome for operators and integrators. Deep contract reference: Enterprise MCP and Enterprise MCP reference.

Builder MCP
Manifest sections datasource.capabilities, datasource.exposedAttributes, datasource.mcpOperations (entity); system certification block
Help topics section, goldenExamples, evidencePatterns, connectedSystemUi
Repair hooks expose, rbac

Publish proof uses CLI show --online and certification pillars — not Builder API upload alone. Ladder: Certification.

How to set

  1. Enable exposure on each Business Entity — exposed.schema, exposed.filterable, and root capabilities[].
  2. Align capability keys with RBAC permission prefixes (customer:get, document:search).
  3. Set datasource externalSpec — authoritative vendor operation source for compilation (system OpenAPI is connectivity only).
  4. Upload and verify online contract:
aifabrix repair <systemKey> --expose
aifabrix validate <systemKey>
aifabrix upload <systemKey> --probe
aifabrix show <systemKey> --online
  1. Run certification pillars before production Role Assistant use.

Defaults and examples

Enterprise MCP tools map to deduplicated business capability keys — one tool per governed action. Tool inputs use normalized metadata from fieldMappings, not vendor field names.

Check Command / surface
Compiled contract online aifabrix show <systemKey> --online
Operations proof aifabrix verify-operations <systemKey>
Trust metadata aifabrix verify-trust <systemKey>
Governance aifabrix verify-governance <systemKey>

Validate

aifabrix show <systemKey> --online
aifabrix verify-operations <systemKey>
aifabrix test-e2e <systemKey>

Common mistakes

Mistake Fix
Testing MCP before upload Upload first; local JSON is not the contract
System OpenAPI treated as entity contract Set externalSpec per Business Entity
Decorative capability keys Match capabilities[].key to CIP/OpenAPI operations
Skipping governance pillar Run full certification ladder
Related articles