Pipefork is a browser-based API building tool whose main purpose is to help developers integrate multiple scattered APIs into a single clean endpoint without setting up an additional backend. It is suitable for developers and small teams building frontend backends, partner integrations, internal tools, and AI agent workflows.
Main capabilities:
- Compose responses: Call multiple HTTP APIs and merge their results into a single JSON response. For example, you can integrate data from a CRM system and a billing system to return a customer overview.
- AI Builder: Describe endpoint requirements in natural language, and the AI will create an API draft for users to review and test.
- Endpoint management: From draft to publication, it supports configuring upstream calls, mapping response fields, and protecting upstream credentials from being exposed.
- Secure publishing: Protect endpoints with API keys and gradually roll out versions through the Dev, Test, and Prod environments.
- MCP integration: Through the Model Context Protocol (MCP), authorized AI clients can manage the Pipefork workspace, including creating and updating projects, preparing drafts, and managing deployments; it can also expose published endpoints as tools that AI can call.
How to use:
- Start in the browser: Design the endpoint manually, or tell AI Builder what the endpoint should do. Then add upstream HTTP API calls, configure data passing between steps, shape and protect the response, and finally test the draft and deploy it to Dev, then promote it to Test and Prod.
- Connect AI tools through MCP: First copy the Management MCP server URL from Pipefork, add it to the AI tool, log in, and approve workspace access. For example, in ChatGPT, enable developer mode and add a personal plugin, then paste the MCP URL to complete authorization; in Cursor, add a remote server through mcp.json; in Claude, add a web connector through a custom connector. Any compatible remote MCP client is also supported.
- Call the MCP endpoint of a published API: Have the AI client call the deployed endpoint tool, using that API's own MCP URL (obtained from its publication documentation).
Applicable scenarios:
- Developers and small teams building frontend backends, partner integrations, internal tools, and AI agent workflows.
- Need to integrate multiple APIs into a single endpoint,and scenarios where you want to avoid building an extra backend.
- You want AI clients to be able to manage and invoke automated workflows for APIs.
- Safely publish and manage API versions across development, testing, and production environments.
Limits and plans:
- Free plan: For evaluation and development only, with no production commitment and no credit card required. It provides building and testing in Dev, API key protection, and basic usage limits.
- Paid plan (available at launch): For real production projects, including Dev, Test, and Prod deployments, higher project and request limits, more API keys, and longer log retention.
- Team plans (Team and Enterprise): For larger API portfolios, providing higher request and rate limits, extended log retention, and management for team size. On Team and Enterprise plans, connectors must first be added by the owner.
Other notes: Pipefork is currently in Beta, and free use requires no credit card. Using MCP features requires an AI client that supports remote MCP, OAuth, and the registration method enabled by Pipefork. Specific pricing and paid plan details are not yet available.