Air Pipe
Build, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.
Community: Submitted by a user or imported; check the owner before granting accessOnlineAPI 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.
Server tool list (19)
Raw names from tools/list. Only developers need these.
| update_module | Update an existing reusable module by module_uuid (adds a new revision; spec_yaml is base64-encoded YAML) and optionally redeploy. |
| 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). |
| 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. |
| list_configs | List the organization's AirPipe configurations. |
| list_organizations | List the organizations you belong to and their organization_uuid. Call this first to get an organization_uuid for the config tools. |
| deploy_module_revision | Deploy a specific past revision of a module to staging or production. |
| 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. |
| get_config | Get a single configuration's data by config_uuid, optionally with its revisions. |
| list_modules | List the organization's reusable modules (pass revisions=true to include revision history). |
| get_module | Get a single reusable module by uuid, including its revision history and spec. |
| update_config | Update an existing AirPipe configuration by config_uuid (config_yaml is base64-encoded YAML) and optionally redeploy. |
| undeploy_module | Undeploy a reusable module from an environment (STAGING or PRODUCTION). |
| create_config | Create a new AirPipe configuration (config_yaml is base64-encoded YAML) and optionally deploy it to staging or production. |
| undeploy_config | Undeploy a configuration from an environment (STAGING or PRODUCTION). |
| delete_config | Delete one or more AirPipe configurations by config_uuid. |
| delete_module | Delete one or more reusable modules by module_uuid. |
| toggle_config | Enable or disable one or more configurations by config_uuid. |
| edit_config | Edit an AirPipe configuration YAML with a natural-language instruction. |
| deploy_config_revision | Deploy a specific past revision of a configuration to staging or production. |