What channels can an Alfe bot use?

Per Alfe's integrations, bots can operate across Slack, Microsoft Teams, Discord, Google Workspace, web/mobile chat, and phone (SMS and voice via Twilio).

Does Alfe keep memory across channels?

Yes. Alfe's Sync integration backs files, conversations, and memory to the cloud so context persists across channels.

Yes. Alfe positions itself as "MCP-native" and exposes a public MCP endpoint at mcp.alfe.ai with a /.well-known/agent.json discovery document, so an agent can connect over MCP and bootstrap the platform — claiming compute, an identity, and channels — with no human in the loop.

ManagedNot yet hands-on tested

Alfe

Build, deploy, and run bots across chat, voice, and messaging channels from one managed platform.

What it is

Alfe is a managed platform for creating, deploying, and running AI bots/agents across messaging and voice channels, providing a control plane for permissions, memory, integrations, and a dashboard. It can also connect to an existing agent rather than only hosting new ones.

At a glance

6/7 facts sourced

Pricing: Freemium — the site describes a tenant-wide credit pool that funds compute, model usage, voice, channels, and storage, plus optional per-agent subscriptions, and is self-serve from the dashboard; no specific dollar figures or tier table are published in a verifiable form.Unverified
Hosting model: Managed cloud control plane, with a Sync integration backing config, files, and memory to the cloud.source ↗
Memory & state: Built-in cross-channel memory: the Sync integration backs files, conversations, and memory to the cloud so context persists across channels.source ↗
MCP support: Nativesource ↗
Integrations: Voice (Twilio + Discord), Discord, web/mobile chat, SMS + calls via Twilio, Google Workspace (Meet/Calendar/Drive), Microsoft Teams, Slack, and Sync.source ↗
Model providers: Nine model providers behind one proxy per Alfe's site — Anthropic, OpenAI, Gemini, DeepSeek, Mistral, xAI, OpenRouter, Zhipu, and MiniMax — with per-tenant policy and BYOK overrides.source ↗
Open source: Nosource ↗

3.3of 5

Editorial scorecard

Overall 3.3 / 5

Our opinion — the same 0–5 rubric is applied to every platform, including Alfe. See the rubric.

Developer experience3/5

Pricing transparency & value2/5

Scalability3/5

Memory & state4/5

Integrations4/5

MCP nativeness4/5

Strengths

MCP-native: a public MCP endpoint (mcp.alfe.ai) with a .well-known/agent.json discovery document lets an agent bootstrap the platform — claim compute, identity, and channels — over MCP.
Broad out-of-the-box channel coverage — Slack, Teams, Discord, Google Workspace, web chat, and phone/SMS via Twilio.
Nine model providers behind one proxy with per-tenant policy and BYOK, so you can switch models without rotating keys.
Cross-channel memory is built in via the Sync integration.
Can act as a managed control plane over an existing agent, not just newly created ones.

Trade-offs

No published dollar figures or tier table — the pricing model is described publicly but the numbers are not.
The integration framework is licensed for internal use only, not open source.
Developer-facing documentation (SDK reference, tutorials) is thinner in public than the framework leaders.

Our take

Editorial opinion — not a hands-on test result

In our opinion, Alfe reads as a breadth-first managed option with a genuinely MCP-native front door: it publishes a public MCP endpoint (mcp.alfe.ai) whose discovery document lets an agent bootstrap the whole platform — compute, identity, channels — over MCP, and it routes nine model providers behind one proxy. Its other strengths are turnkey channel coverage and built-in cross-channel memory. The main gap is transparency of the paid surface: the pricing model is described publicly but no dollar figures are published, so teams that need those specifics up front should confirm directly. Held to the same rubric as everything else here, it sits mid-pack: strong on MCP nativeness, memory, and integrations, but behind the leaders on published pricing and depth of public developer docs.

FAQ

What channels can an Alfe bot use?: Per Alfe's integrations, bots can operate across Slack, Microsoft Teams, Discord, Google Workspace, web/mobile chat, and phone (SMS and voice via Twilio).
Does Alfe keep memory across channels?: Yes. Alfe's Sync integration backs files, conversations, and memory to the cloud so context persists across channels.
Is Alfe MCP-native?: Yes. Alfe positions itself as "MCP-native" and exposes a public MCP endpoint at mcp.alfe.ai with a /.well-known/agent.json discovery document, so an agent can connect over MCP and bootstrap the platform — claiming compute, an identity, and channels — with no human in the loop.

Compare Alfe

Sources

Alfe homepage · accessed 2026-07-01
Alfe public MCP discovery document · accessed 2026-07-01
AlfeAI GitHub organization · accessed 2026-07-01
alfe-integrations repository · accessed 2026-07-01

The Agent Examiner editorial · last updated 2026-07-01. Facts are drawn from each vendor’s own public materials; scores are our editorial opinion (methodology).

Product and company names are trademarks of their respective owners and are used here only to identify the products under discussion.