Der Air Pipe MCP-Server,
verbunden mit einem Klick.

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

“Nutze „create_module“: Create a reusable module (a typed config fragment referenced by handle) and optionally deploy it to staging or production. spec_yaml is base.”

“Nutze „validate_config“: Schema-validate an airpipe YAML config. Send { "yaml": <the full YAML string> }. Returns { valid: true } when it passes, or { valid: false,.”

“Nutze „list_configs“: List the organization's AirPipe configurations.”

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 base

validate_config — Schema-validate an airpipe YAML config. Send { "yaml": <the full YAML string> }. Returns { valid: true } when it passes, or { valid: false,

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)

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