Skip to content
Combine
Get started

COMBINE FOR AGENTS

One connection.
Your whole toolkit.

Combine’s Ash-backed MCP gateway discovers your services and routes explicitly allowed tools using your own product credentials.

Connect in three steps

  1. 01 / Sign in with Citadel and connect an existing product account.
  2. 02 / Choose the exact tool names that your agent may call.
  3. 03 / Create a Combine API key and add this remote HTTP server to your MCP client.
Manage connections

Streamable HTTP

https://combine.g.combine.mesa.ws/mcp 

{
  "mcpServers": {
    "combine": {
      "url": "https://combine.g.combine.mesa.ws/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_COMBINE_API_KEY"
      }
    }
  }
}

Use your client’s secret storage for the token. Keys expire after 90 days and can be revoked from your workspace. Client-specific HTTP configuration may differ.

A clear view of what’s connected.

Identity and billing are shared foundations. Operational tools depend on each product’s public API and your credentials.

Citadel

Direct access

Register each application in a Citadel space. Customer-space setup is operator-assisted.

Mesa

Product MCP

Connect a Mesa personal API token with access to your servers. Hosting is configured separately.

Hevsuit

Product MCP

An operator creates the project and its provider token. Browser access currently requires an admin or operator role.

Cablebox

Direct access

Open your organization in Cablebox. Central provisioning and customer MCP are not available yet.

Reca

Product MCP

Connect your own Reca application key for your payment data. Combine's sales account remains separate.

Fabrica Mail

Product MCP

Use an application token to send email, or a Fabrica user token for management. A Postmark connection and verified sender are required.

Discovery before action

Start with discover_products and list_my_services. Use list_service_tools to retrieve the upstream schemas, then call_service_tool with a product ID, tool name and its original arguments. Nested input shapes are preserved. A service’s tool result is distinct from the final status of an asynchronous deployment, email or payment.