Air Pipe

Build, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.

CommunityOnlineAPI key requiredGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    An API key from the service settings is required

    Build, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.

    How to connect

    How to connect Air Pipe to Claude

    The server address to paste into Claude settings:

    https://api.airpipe.io/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect Air Pipe to ChatGPT

    The server address to paste into ChatGPT settings:

    https://api.airpipe.io/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect Air Pipe to Cursor

    The server address to paste into Cursor settings:

    https://api.airpipe.io/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (19)

    Raw names from tools/list. Only developers need these.

    update_moduleUpdate an existing reusable module by module_uuid (adds a new revision; spec_yaml is base64-encoded YAML) and optionally redeploy.
    create_moduleCreate a reusable module (a typed config fragment referenced by handle) and optionally deploy it to staging or production. spec_yaml is base64-encoded YAML of the module body; module_type is the config struct it represents (e.g. Database).
    validate_configSchema-validate an airpipe YAML config. Send { "yaml": <the full YAML string> }. Returns { valid: true } when it passes, or { valid: false, error: <message> } when it fails — feed the error back into your fix and call again until valid. Schema check only; does not save. Use create_config to persist a valid config.
    list_configsList the organization's AirPipe configurations.
    list_organizationsList the organizations you belong to and their organization_uuid. Call this first to get an organization_uuid for the config tools.
    deploy_module_revisionDeploy a specific past revision of a module to staging or production.
    plan_configGet airpipe config-authoring instructions plus RAG-retrieved real action examples for a natural-language request, so YOU (the calling model) write the YAML yourself instead of the server generating it. Returns { instructions, context, request, protocol }. After writing the config, validate it with the validate_config tool (repair loop) then persist it with create_config. Prefer this over generate_config whenever you can author YAML yourself.
    get_configGet a single configuration's data by config_uuid, optionally with its revisions.
    list_modulesList the organization's reusable modules (pass revisions=true to include revision history).
    get_moduleGet a single reusable module by uuid, including its revision history and spec.
    update_configUpdate an existing AirPipe configuration by config_uuid (config_yaml is base64-encoded YAML) and optionally redeploy.
    undeploy_moduleUndeploy a reusable module from an environment (STAGING or PRODUCTION).
    create_configCreate a new AirPipe configuration (config_yaml is base64-encoded YAML) and optionally deploy it to staging or production.
    undeploy_configUndeploy a configuration from an environment (STAGING or PRODUCTION).
    delete_configDelete one or more AirPipe configurations by config_uuid.
    delete_moduleDelete one or more reusable modules by module_uuid.
    toggle_configEnable or disable one or more configurations by config_uuid.
    edit_configEdit an AirPipe configuration YAML with a natural-language instruction.
    deploy_config_revisionDeploy a specific past revision of a configuration to staging or production.