Tool invocation
Call approved MCP tools with workflow-provided context.
MCP Component
MCP Component for customer-owned automation.
Use MCP Component when a workflow should invoke an approved AI-facing tool as part of a larger process.
Call approved Model Context Protocol tools from inside a governed CXFabric flow.
MCP Component
Component
MCP ComponentCall services, send messages, and complete work in downstream systems.
CX
CXFabric Flow
Rules, credentials, validation, audit
SettingsInputs and options
LogsRun history and output
Next stepConnector, component, or approval
What this component unlocks
Use MCP Component as a visible flow step.
MCP Component keeps tool calls visible and governed inside the workflow path. This page is a CXFabric website template for MCP component patterns and can be expanded as formal product documentation grows.
Policy checks
Validate tool inputs and route sensitive actions through approval steps.
Logged outcomes
Capture tool outputs, errors, and follow-up actions in workflow history.
Use cases
Where MCP Component fits in automation.
These examples show how this component can become part of production workflows across customer-owned systems and environments.
AI tool call
Use MCP Component as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Private knowledge lookup
Use MCP Component as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Agent workflow step
Use MCP Component as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Approved data action
Use MCP Component as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Tool result validation
Use MCP Component as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Human-in-the-loop automation
Use MCP Component as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Configuration surface
Practical options builders expect to use.
The exact fields can vary by deployment and product version, but each page gives customers a clear view of the component's intended role.
Select MCP tool
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Map input context
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Validate request
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Invoke tool
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Handle response
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Log tool output
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Implementation notes
Design the step with operations in mind.
Components should be easy for builders to configure and easy for operators to understand after the workflow is live.
Website planning page
This component detail page is a CXFabric website template and can be expanded as formal documentation grows.
Keep tool access scoped
Keep tool access scoped.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Validate tool output before system updates
Validate tool output before system updates.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Separate AI reasoning from execution rules
Separate AI reasoning from execution rules.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Workflow patterns
Reusable patterns for MCP Component.
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
MCP Component in a customer intake flow
Start with an event, use MCP Component, then route the result to CRM, ticketing, or a customer-owned system.
MCP Component with approval and audit
Add validation, human approval, and logging around the component before downstream actions execute.
MCP Component in a private runtime
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
MCP Component plus custom connector
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
Need MCP Component inside a customer workflow?
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.