mcp server
Pipe2.ai
Run multi-step AI pipelines for video, image, audio and text: upload media, run, poll results.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-07-31.
What this server can do
5 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_pipeline_run_status(run_id)- Check the status of a pipeline run. Returns status (pending/running/completed/failed), output data, error messages, timestamps, and generated asset URLs. Required: run_id.
get_pipeline_schema(pipeline_slug)- Get the input schema for a specific pipeline. Returns the JSON Schema describing required and optional input fields. Use this before running a pipeline to understand what inputs are needed. Required: pipeline_slug.
list_pipelines- List all available AI video/image pipelines. Returns name, slug, description, category, credit cost, and required providers for each active pipeline.
request_upload(filename, content_type)- Request a presigned S3 upload URL for a file. Use this for pipeline inputs that require file URLs (e.g., images, videos, audio). **Two-step upload flow:** 1. Call this tool with filename and content_type to get a presigned upload URL and final asset URL 2. PUT the file contents to the upload_url (presigned, expires in 5 minutes) 3. Use the asset_url as the input value when running a pipeline Supported content types: image/* (max 10MB), video/* (max 50MB), audio/* (max 20MB) Required: filename, content_type.
run_pipeline(input, pipeline_slug)- Run an AI pipeline by slug with the given input. Use list_pipelines to discover available pipelines and get_pipeline_schema to see required inputs. Returns a run ID for tracking status. Required: pipeline_slug, input.
Last successful function declaration observed on . Source: https://mcp.pipe2.ai/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.pipe2.ai/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-31 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-31 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 5 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.pipe2.ai | |
| mcp endpoint status | ok | The server listed 5 functions when asked. | as of probe | mcp.pipe2.ai |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json