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.
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
Endpoints
remote
auth
reachable
uptime 30d
p50
protocol
last ok
https://api.airpipe.io/mcpstreamable-http
api_key ${AIRPIPE_TOKEN}
yes
100%
329 ms
2025-11-25
2026-10-20
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.