Reaching your systems
It speaks the protocol, in both directions.
Most platforms hand-build one connector per service, so you wait for whichever integration is next on a roadmap. AiFlow implements MCP itself, which means a compliant server works the day it ships.
What the capability actually does.
Gallery of servers, one click
A browsable gallery of vendor-hosted MCP servers, grouped by category and verified end to end by us. Notion, Linear, Atlassian, Stripe, Cloudflare, Sentry, Supabase, PagerDuty, Datadog, and more. Anything not listed still connects by pasting its URL.
Connect out, without a connector
OAuth 2.1 with PKCE and dynamic client registration, so authorising a new service is a click rather than a connector we have to write. Available to Orchestrators as well as agents.
And serve as one, scoped
Outside clients can drive your deployment: place a call, search the knowledge base, fetch a transcript, list agents, record an event, look up a contact, call a custom tool, delegate to an Orchestrator. Each capability has its own API key scope, with no wildcard by design, and every call lands in the audit log.
Native CRM where it helps
Salesforce and HubSpot have first-class connectors with OAuth and encrypted tokens, giving agents tools to upsert a contact, open a ticket, and log call activity without going through MCP at all.
Or describe your own tool
Name an action, describe what it needs, and point it at an HTTP endpoint you control. AiFlow calls it and hands the result back to the agent.
The screens this happens on.
Built in and yours
Built-in tools, and everything you extend the agent with. Each one is enabled per agent, so two agents on the same deployment can carry very different capabilities. A tool the licence does not cover is never registered at all, which means the model is unaware of it rather than being told it may not use it.
- Custom HTTP tools, MCP connections, and delegation links all appear here
Gallery of servers, one click each
Vendor-hosted MCP servers, grouped by category and verified end to end by us, each connecting in a click. Anything not listed still connects by pasting its URL, because AiFlow implements the protocol rather than one connector per service. It is a curated gallery, not a marketplace: nobody can list their own.
- OAuth 2.1 with PKCE and dynamic client registration
- Streamable HTTP only, never a local stdio process
What it deliberately does not do.
- Streamable HTTP transport only. Servers that run as a local process over stdio are not supported.
- The catalog is curated rather than open. Nobody can list their own server in it, and the entries are ones we verified.
- There is no native Zendesk connector. The integration runs the other way, with Zendesk calling into AiFlow as an MCP client.
- Custom tools and MCP are declared, schema-bound integrations. Neither is a way to upload and execute arbitrary code, which is deliberate.