Skip to content

Air Pipe

by airpipe.io · remote · no sign-in to list tools · v2026.7.28 · published by io.airpipe

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

Deletes · 2Changes · 10
CompareRegistry entry

19 tools: 2 can delete or cancel things, 10 change things and 7 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http airpipe https://api.airpipe.io/mcp --header 'Authorization: <your-authorization>'

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

19 tools

Deletes or cancels 2Claude Code: deny
  • delete_configDelete one or more AirPipe configurations by config_uuid.No findings

    Why it is in this group

    • The name "delete_config" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete one or more AirPipe configurations by config_uuid.
  • delete_moduleDelete one or more reusable modules by module_uuid.No findings

    Why it is in this group

    • The name "delete_module" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete one or more reusable modules by module_uuid.
Changes things 10Claude Code: ask
  • create_configCreate a new AirPipe configuration (config_yaml is base64-encoded YAML) and optionally deploy it to staging or production.No findings

    Why it is in this group

    • The name "create_config" says "create": a word for a change.
    Description, as the server wrote it
    Create a new AirPipe configuration (config_yaml is base64-encoded YAML) and optionally deploy it to staging or production.
  • create_moduleCreate a reusable module (a typed config fragment referenced by handle) and optionally deploy it to staging or production.No findings

    Why it is in this group

    • The name "create_module" says "create": a word for a change.
    Description, as the server wrote it
    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).
  • deploy_config_revisionDeploy a specific past revision of a configuration to staging or production.No findings

    Why it is in this group

    • The name "deploy_config_revision" says "deploy": a word for a change.
    Description, as the server wrote it
    Deploy a specific past revision of a configuration to staging or production.
  • deploy_module_revisionDeploy a specific past revision of a module to staging or production.No findings

    Why it is in this group

    • The name "deploy_module_revision" says "deploy": a word for a change.
    Description, as the server wrote it
    Deploy a specific past revision of a module to staging or production.
  • edit_configEdit an AirPipe configuration YAML with a natural-language instruction.No findings

    Why it is in this group

    • The name "edit_config" says "edit": a word for a change.
    Description, as the server wrote it
    Edit an AirPipe configuration YAML with a natural-language instruction.
  • toggle_configEnable or disable one or more configurations by config_uuid.No findings

    Why it is in this group

    • The name "toggle_config" says "toggle": a word for a change.
    Description, as the server wrote it
    Enable or disable one or more configurations by config_uuid.
  • undeploy_configUndeploy a configuration from an environment (STAGING or PRODUCTION).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Undeploy a configuration from an environment (STAGING or PRODUCTION).
  • undeploy_moduleUndeploy a reusable module from an environment (STAGING or PRODUCTION).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Undeploy a reusable module from an environment (STAGING or PRODUCTION).
  • update_configUpdate an existing AirPipe configuration by config_uuid (config_yaml is base64-encoded YAML) and optionally redeploy.No findings

    Why it is in this group

    • The name "update_config" says "update": a word for a change.
    Description, as the server wrote it
    Update an existing AirPipe configuration by config_uuid (config_yaml is base64-encoded YAML) and optionally redeploy.
  • update_moduleUpdate an existing reusable module by module_uuid (adds a new revision; spec_yaml is base64-encoded YAML) and optionally redeploy.No findings

    Why it is in this group

    • The name "update_module" says "update": a word for a change.
    Description, as the server wrote it
    Update an existing reusable module by module_uuid (adds a new revision; spec_yaml is base64-encoded YAML) and optionally redeploy.
Only reads 7Claude Code: allow
  • get_configGet a single configuration's data by config_uuid, optionally with its revisions.No findings

    Why it is in this group

    • The name "get_config" says "get": a word for reading.
    Description, as the server wrote it
    Get a single configuration's data by config_uuid, optionally with its revisions.
  • get_moduleGet a single reusable module by uuid, including its revision history and spec.No findings

    Why it is in this group

    • The name "get_module" says "get": a word for reading.
    Description, as the server wrote it
    Get a single reusable module by uuid, including its revision history and spec.
  • list_configsList the organization's AirPipe configurations.No findings

    Why it is in this group

    • The name "list_configs" says "list": a word for reading.
    Description, as the server wrote it
    List the organization's AirPipe configurations.
  • list_modulesList the organization's reusable modules (pass revisions=true to include revision history).No findings

    Why it is in this group

    • The name "list_modules" says "list": a word for reading.
    Description, as the server wrote it
    List the organization's reusable modules (pass revisions=true to include revision history).
  • list_organizationsList the organizations you belong to and their organization_uuid.No findings

    Why it is in this group

    • The name "list_organizations" says "list": a word for reading.
    Description, as the server wrote it
    List the organizations you belong to and their organization_uuid. Call this first to get an organization_uuid for the config tools.
  • 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 …No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    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.
  • validate_configSchema-validate an airpipe YAML config.No findings

    Why it is in this group

    • The name "validate_config" says "validate": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 2026.7.28. Values in angle brackets are yours to fill in.

claude mcp add --transport http airpipe https://api.airpipe.io/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__airpipe__validate_config",
      "mcp__airpipe__list_organizations",
      "mcp__airpipe__list_configs",
      "mcp__airpipe__list_modules",
      "mcp__airpipe__get_module",
      "mcp__airpipe__plan_config",
      "mcp__airpipe__get_config"
    ],
    "ask": [
      "mcp__airpipe__edit_config",
      "mcp__airpipe__undeploy_module",
      "mcp__airpipe__undeploy_config",
      "mcp__airpipe__create_module",
      "mcp__airpipe__deploy_module_revision",
      "mcp__airpipe__update_module",
      "mcp__airpipe__create_config",
      "mcp__airpipe__toggle_config",
      "mcp__airpipe__deploy_config_revision",
      "mcp__airpipe__update_config"
    ],
    "deny": [
      "mcp__airpipe__delete_module",
      "mcp__airpipe__delete_config"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as airpipe. Review it before you use it.