Air Pipe

io.airpipePublished by airpipe.ioOfficial publisherv2026.7.28Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Air Pipe is a remote MCP server that lets an assistant author, validate, deploy and manage AirPipe configurations and reusable modules.

What you can do
List organizations, configurations and reusable modules, and read a single config or module with its revision history and spec, optionally including revisions in listings. Author and edit configuration YAML from natural-language instructions, including a planning step that returns authoring guidance and retrieved examples for the model to write the YAML itself. Schema-validate YAML before saving, and create or update configurations and modules from base64-encoded YAML. Deploy, redeploy or undeploy configurations and modules to staging or production, including specific past revisions. Enable or disable configurations, and delete configurations or modules by UUID.
When to use it
Useful when you manage AirPipe resources from an AI client and want the assistant to draft, check and ship configuration changes, or to inspect and roll back revisions, without switching to the AirPipe web app.
Requirements
A remote streamable HTTP endpoint at the provider's API host. An Air Pipe API token is required as a bearer credential in the Authorization header, created in the AirPipe web app. No local runtime or environment variables are declared.
Before you install
The Authorization bearer token is a secret and grants access to your organization's resources. Many tools change live state: create, update, deploy, redeploy, undeploy, enable/disable and delete configurations and modules, including to production. Deletions and production deployments should be confirmed before running. Configurations and modules are sent to the AirPipe service.

Installation

In SourceWeft

  1. Open Air Pipe in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.airpipe%2Fairpipe/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "air-pipe": {
      "type": "http",
      "url": "https://api.airpipe.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

19

update_module

Update an existing reusable module by module_uuid (adds a new revision; spec_yaml is base64-encoded YAML) and optionally redeploy.

Parametershandlerequiredrole_uuidspec_yamlrequiredpermissiondescriptionmodule_typerequiredmodule_uuiddeploy_stagingdeploy_productionorganization_uuid

edit_config

Edit an AirPipe configuration YAML with a natural-language instruction.

Parametersinstructionrequiredcurrent_yamlrequiredorganization_uuidrequired

toggle_config

Enable or disable one or more configurations by config_uuid.

Parametersconfig_uuidsrequiredorganization_uuidrequired

undeploy_config

Undeploy a configuration from an environment (STAGING or PRODUCTION).

Parametersconfig_uuidrequiredenvironmentrequiredorganization_uuidrequired

create_module

Create 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).

Parametershandlerequiredrole_uuidspec_yamlrequiredpermissiondescriptionmodule_typerequireddeploy_stagingdeploy_productionorganization_uuid

deploy_module_revision

Deploy a specific past revision of a module to staging or production.

Parametersmodule_uuidrequiredrevision_uuidrequiredorganization_uuidrequired

delete_module

Delete one or more reusable modules by module_uuid.

Parametersmodule_uuidsrequiredorganization_uuidrequired

get_config

Get a single configuration's data by config_uuid, optionally with its revisions.

Parametersconfig_uuidrequiredorganization_uuidrequired

undeploy_module

Undeploy a reusable module from an environment (STAGING or PRODUCTION).

Parametersenvironmentrequiredmodule_uuidrequiredorganization_uuidrequired

get_module

Get a single reusable module by uuid, including its revision history and spec.

Parametersmodule_uuidrequiredorganization_uuidrequired

plan_config

Get 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.

Parameterslimitrequestrequiredorganization_uuid

deploy_config_revision

Deploy a specific past revision of a configuration to staging or production.

Parametersconfig_uuidrequiredrevision_uuidrequiredorganization_uuidrequired

delete_config

Delete one or more AirPipe configurations by config_uuid.

Parametersconfig_uuidsrequiredorganization_uuidrequired

list_organizations

List the organizations you belong to and their organization_uuid. Call this first to get an organization_uuid for the config tools.

Takes no parameters.

list_modules

List the organization's reusable modules (pass revisions=true to include revision history).

Parametersorganization_uuidrequired

create_config

Create a new AirPipe configuration (config_yaml is base64-encoded YAML) and optionally deploy it to staging or production.

Parametersrole_uuidpermissionconfig_yamlrequireddeploy_stagingdeploy_productionorganization_uuid

update_config

Update an existing AirPipe configuration by config_uuid (config_yaml is base64-encoded YAML) and optionally redeploy.

Parametersrole_uuidpermissionconfig_uuidconfig_yamlrequireddeploy_stagingdeploy_productionorganization_uuid

validate_config

Schema-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.

Parametersyamlrequired

list_configs

List the organization's AirPipe configurations.

Parametersorganization_uuidrequired

Version history

1
  1. v2026.7.28LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.