Skip to content
alfe.aiDocs

MCP on Alfe

Alfe is MCP-native on both sides of the Model Context Protocol:

  • Alfe exposes a public MCP server. An agent can discover the platform, onboard itself, install integrations, and manage its own tokens through MCP tool calls, with no dashboard required. That’s the server at mcp.alfe.ai, described below.
  • Every Alfe agent consumes MCP servers as tools. You can attach MCP servers to an agent — curated ones that ship as integrations, or your own local and remote servers — and their tools become part of the agent’s toolset. See Use MCP servers with your agent.

The rest of this page covers the public server Alfe exposes.

The public endpoint

Section titled “The public endpoint”

The MCP server is available at:

https://mcp.alfe.ai/mcp

It speaks the Streamable HTTP transport:

  • POST /mcp — send JSON-RPC requests (start with initialize).
  • GET /mcp — receive server-to-client notifications.
  • DELETE /mcp — end the session.

After you initialize, the server returns a session id. Include it as the Mcp-Session-Id header on every subsequent request. A legacy HTTP+SSE transport is also available at https://mcp.alfe.ai/sse for older clients.

Discovery

Section titled “Discovery”

Alfe publishes a discovery document so agents and tools can find the endpoint and see what the platform offers:

GET https://mcp.alfe.ai/.well-known/agent.json

The document describes Alfe, points to the MCP endpoint (and the legacy SSE endpoint), lists high-level capabilities, and tells clients how to get started — connect to the MCP endpoint and call alfe_describe_platform.

Connecting a client

Section titled “Connecting a client”

Any MCP-capable client can connect. Point it at https://mcp.alfe.ai/mcp, initialize a session, and start calling tools. A typical first sequence:

  1. alfe_describe_platform — learn what Alfe offers.
  2. alfe_check_requirements — check prerequisites and see the onboarding flow.
  3. Onboard with one of the paths in Agent-led bootstrap.

What the tools cover

Section titled “What the tools cover”

Before onboarding, a small set of unauthenticated tools handle discovery and sign-up. Once a session is authenticated (by bootstrapping, joining via an invite, or authenticating with an existing API key), a much larger toolset becomes available, including:

  • Agents — update, start, stop, reboot, recreate, upgrade, delete, and check the status of agents.
  • Integrations — browse, list, install, configure, and remove integrations, and start OAuth flows.
  • Billing — check balance and plans, list transactions, and configure auto-recharge.
  • Usage — read usage for the organization or one agent.
  • Tokens — create, list, and revoke API tokens, for example for sub-agents.
  • Templates — browse the marketplace and install or fork templates.
  • Webhooks — create endpoints, rotate signing secrets, and inspect deliveries.
  • Organization — list teams and projects, view members and goals, and set the agent’s active context.
  • Referrals and promotions — read a referral code and redeem a code.

What a key can do

Section titled “What a key can do”

Authenticating doesn’t unlock every tool. A session can only do what its API key’s scopes allow:

  • Agent-scoped tools act on the session’s own agent. A session authenticated as one agent can’t act on another.
  • Tenant-wide tools need a key with the admin scope. These include creating and listing agents, financial data, organization-wide usage, invites, referrals, and template writes.

Continue to Agent-led bootstrap for the onboarding flows.

Connect your own assistant

Section titled “Connect your own assistant”

People can also connect a supported assistant, such as ChatGPT or Claude, to their Alfe account. This uses a separate endpoint and OAuth instead of an agent’s API key:

https://mcp.alfe.ai/account/mcp

You approve the connection in the dashboard and choose which agents the assistant can see. It’s read-only discovery today, with three tools: alfe_get_account, alfe_list_agents, and alfe_get_agent. It can’t chat with an agent or send it tasks. To revoke a connection, use Assistant access in your account settings.

The other side: agents that consume MCP

Section titled “The other side: agents that consume MCP”

Beyond the public server, every Alfe agent can use MCP servers as tools: