MCP.so
Sign In
D

delete MCP Server

Basic information

Transport

Streamable HTTP

Authentication

Check provider docs

Last updated

Submitted by

Kav Pather

About delete MCP Server

delete delete delete

Connection details

https://api.airpipe.io/mcp

Setup

claude mcp add delete --transport http https://api.airpipe.io/mcp

delete MCP Server tools

19

List the organization's reusable modules (pass revisions=true to include revision history).

Enable or disable one or more configurations by config_uuid.

Delete one or more reusable modules by module_uuid.

Edit an AirPipe configuration YAML with a natural-language instruction.

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.

Create a new AirPipe configuration (config_yaml is base64-encoded YAML) and optionally deploy it to staging or production.

List the organization's AirPipe configurations.

Deploy a specific past revision of a module to staging or production.

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 a single configuration's data by config_uuid, optionally with its revisions.

Deploy a specific past revision of a configuration to staging or production.

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).

Update an existing AirPipe configuration by config_uuid (config_yaml is base64-encoded YAML) and optionally redeploy.

List the organizations you belong to and their organization_uuid. Call this first to get an organization_uuid for the config tools.

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

Delete one or more AirPipe configurations by config_uuid.

Undeploy a reusable module from an environment (STAGING or PRODUCTION).

Undeploy a configuration from an environment (STAGING or PRODUCTION).

Get a single reusable module by uuid, including its revision history and spec.

Frequently asked questions

1

What is the delete remote MCP server?

The delete remote MCP server is a hosted Model Context Protocol endpoint at https://api.airpipe.io/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the delete MCP server?

Add the endpoint https://api.airpipe.io/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the delete MCP server require authentication?

Authentication requirements for delete have not been confirmed in this listing. Check the provider’s documentation before connecting.

4

Which transport does the delete MCP server use?

delete exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments