# Air Pipe

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

- name: io.airpipe/airpipe
- version: 2026.7.28
- connection class: R1 (autonomous)
- trust: 80/100 flags: no-repository
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.airpipe%2Fairpipe
- tools: https://api.protogrid.dev/v1/servers/io.airpipe%2Fairpipe/tools

**An agent can connect on its own if it already holds `AIRPIPE_TOKEN`.** Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "airpipe": {
      "type": "http",
      "url": "https://api.airpipe.io/mcp",
      "headers": {
        "Authorization": "Bearer ${AIRPIPE_TOKEN}"
      }
    }
  }
}
```

Placeholders to fill: `${AIRPIPE_TOKEN}`.

## Trust

- hygiene: 80
- liveness: 100
- freshness: 85
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% ~updated-84d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: create_module (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_config (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); deploy_module_revision (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 1,649 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 19, about 1,649 tokens to load them all
- tool set hash: 0774a1d11309512f2c9a043af5fac920
- badge: [![protogrid quality](https://protogrid.dev/badge/io.airpipe/airpipe.svg)](https://protogrid.dev/servers/io.airpipe/airpipe)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://api.airpipe.io/mcp (streamable-http, auth api_key ${AIRPIPE_TOKEN}, reachable true, uptime30d 1)

## Packages

_none_

## Tools (19)

- `create_config`: Create a new AirPipe configuration (config_yaml is base64-encoded YAML) and optionally deploy it to staging or production.
- `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).
- `delete_config`: Delete one or more AirPipe configurations by config_uuid.
- `delete_module`: Delete one or more reusable modules by module_uuid.
- `deploy_config_revision`: Deploy a specific past revision of a configuration to staging or production.
- `deploy_module_revision`: Deploy a specific past revision of a module to staging or production.
- `edit_config`: Edit an AirPipe configuration YAML with a natural-language instruction.
- `get_config`: Get a single configuration's data by config_uuid, optionally with its revisions.
- `get_module`: Get a single reusable module by uuid, including its revision history and spec.
- `list_configs`: List the organization's AirPipe configurations.
- `list_modules`: List the organization's reusable modules (pass revisions=true to include revision history).
- `list_organizations`: List the organizations you belong to and their organization_uuid. Call this first to get an organization_uuid for the config tools.
- `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.
- `toggle_config`: Enable or disable one or more configurations by config_uuid.
- `undeploy_config`: Undeploy a configuration from an environment (STAGING or PRODUCTION).
- `undeploy_module`: Undeploy a reusable module from an environment (STAGING or PRODUCTION).
- `update_config`: Update an existing AirPipe configuration by config_uuid (config_yaml is base64-encoded YAML) and optionally redeploy.
- `update_module`: Update an existing reusable module by module_uuid (adds a new revision; spec_yaml is base64-encoded YAML) and optionally redeploy.
- `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.