Platform capabilities in detail.
Each page describes a real MCP Fabric building block: how it runs, what it stores, and whether it is core or a licensed add-on. Availability is labeled Available, Preview or Planned.
Agents
A useful agent needs more than a model. It needs the right knowledge, the right tools and a clear boundary around what it is allowed to do. MCP Fabric lets you build specialized agents and connect them to the workflows and capabilities they need.
MCP
Your team may use Claude, Codex, Cursor, Windsurf, OpenClaw or other MCP-compatible clients. You shouldn't have to build the same integration for each one. MCP Fabric provides a governed layer between AI clients and the capabilities they can use.
Identity
Connect MCP Fabric to your company identity so access stays aligned with your people, groups and roles.
Workflows
A workflow is more than a diagram. It defines what happens, in what order, under which conditions and what should happen when a human needs to step in. Create workflows from triggers, agents, knowledge retrieval, decisions, tools, loops, approvals and actions.
Capabilities
RAG
Connect documents to retrieval, agents, chat and workflows. Knowledge stays scoped to the organization using it, so another organization does not see your context.
A2A diagram
A workflow defines what happens, in what order, under which conditions and when a person should step in. What you draw is what runs.
Workflow steps
The steps you can place on the canvas — from triggers and agents to approvals and actions.
SEO monitor
seo-monitor-service runs optional on-page checks and rank tracking (GSC / SERP), Seznam Webmaster indexation, reports and notification e-mails. It is gated by the tenant licence.
Probe
probe-service stores profiles and runs (including ZAP and k6 style jobs) behind a licence gate. Artefacts stay on the probe volume, not in the workflow graph.
Datastore
Business text for retrieval lives in Postgres with pgvector. Binary objects (photos, PDFs to keep) use the licensed files add-on with file-service and MinIO, including admin browse and anonymous drop links.
Connectors
The platform composes tools, capabilities and connections: MCP, REST, SQL, GitHub, SSH, Ansible and other deployed connectors. Calls go through tenant policy and secret references.
Webhook intake
workflow-ingress-service exposes tenant endpoints (publish, disable, retire, revisions, replay). A live example is the Pod Farou contact webhook path into a named workflow with a schema.
Email intake
email-intake-service connects IMAP or Microsoft 365 Graph, stores attachments in file-service, and starts a configured workflow. History, replay, health and OAuth folder pickers live in admin.
Teams
teams-service exposes tenant Teams integration (including OAuth start for a tenant). Messages become workflow or chat traffic under the same RBAC and secret model as other channels.
WhatsApp uses Meta Business API through whatsapp-service. It is not migrated into OpenClaw. Like other customer channels, it is licensed per tenant and calls workflows as tools.
Notifications
notification-service (and related customer notification flows) delivers outbound messages used by SEO reports, operational alerts and workflow steps. SMTP and channel sends use secret-referenced credentials.
Social / OpenClaw
openclaw-bridge plus the OpenClaw gateway handle mobile nodes and Telegram and call published MCP workflows. That path is a licensed `openclaw` add-on and a separate host from admin Nuxt.
Ready to move beyond the chatbot?
Build AI that understands your business, follows your processes and can actually get things done.