An Air Pipe interface becomes an MCP tool with one block of config — same route, same auth, same traces, no second server. Here is the setup for every client we have written up, and the tools are yours, not ours.
Setup guides
Claude Code — CLI — Add the deployment as a Streamable HTTP server and Claude Code can call your interfaces as tools while it works in your repo.
Claude Desktop — Desktop app — Add the deployment's MCP URL as a custom connector. Claude can then read and act through your interfaces in ordinary conversation.
ChatGPT — Connector — Point ChatGPT's custom connector at the deployment's MCP endpoint and your interfaces become tools it can call.
Cursor — Editor — Cursor's agent reads the same tools your HTTP clients call, so it can query and change real data while you build.
Windsurf — Editor — Cascade picks up the deployment's tools and can call them mid-task, with the same auth an HTTP client would need.
VS Code Copilot — Editor — In agent mode, Copilot can call your deployed interfaces as tools without leaving the editor.
Gemini CLI — CLI — Gemini CLI reads MCP servers from its settings file and can then call your interfaces as tools from the terminal.
Zed — Editor — Zed calls MCP servers context servers. Add the deployment there and its assistant can use your tools.
Cline — Editor extension — Cline loads remote MCP servers from its settings file, so your interfaces show up as tools in its task loop.
n8n — Automation platform — n8n can consume your Air Pipe deployment as an MCP tool — which is the honest way to run both: n8n for the canvas, Air Pipe for the backend behind it.