Public API and MCP connector: use echoflow from Claude, Codex or your own systems

echoflow can be used without opening it: an MCP connector, included in every plan, turns it into a tool Claude, Claude Code, ChatGPT, Codex and other compatible assistants can call; with the Pro plan there's also a REST API to integrate it into your systems. Two routes to the same thing, meant for two different people on the same team.

The API, for developers

An agency with forty videos a week doesn't upload them by hand forty times. With the API your system:

• creates a job by sending the file, or opens a resumable chunked upload for large files —

pieces go one at a time and on interruption you resume from the last confirmed offset, exactly as the web app does;

• tracks the state of a job and lists existing ones;
• pulls the outputs when they're ready;
• receives a webhook when content is ready, instead of polling continuously.

Every key has its own rate limit and its own scopes: read for reading content, write for creating jobs, library for querying the archive. A key that only downloads shouldn't be able to spend your minutes.

The MCP connector, for everyone else

Connected once from the assistant, echoflow becomes a tool Claude, Claude Code, ChatGPT and Codex can use. From there you work in plain language: "take the latest episode, pull out the LinkedIn posts and tell me when I talked about pricing".

The assistant can process a video, read the content produced, search the archive and ask questions about your videos. That's the most interesting part: semantic search across years of content becomes available inside the tool you already work in: that, and the API, is where passage search lives.

You connect it with your own account, no keys: when connecting you pick the workspace and what to grant — read, create and process, query the archive — and you can revoke it whenever you like. Every request follows your plan as in the web app. The step-by-step guide is on the Connectors page. For an assistant without OAuth sign-in you use an API key instead, with the same scopes: that's on the Pro plan.

What we don't do

• We don't publish to social, not even via API: there are no endpoints that write to your channels,

because we don't store social tokens. The API returns content, not publications.

• There's no official client library for a specific language: it's a REST API, called like any

other.

• The API doesn't bypass plan limits: file size, duration and minutes apply identically on the

programmatic channel. Past the ceiling you get a clear error with a code, not a 500.

• Media files pulled via API stay available for 7 days as in the app; text doesn't expire while the account stays active.

Which plan

The MCP connector with sign-in from your own account is included in every plan, trial included, at no extra cost. Public API, webhooks, chunked upload via API and API keys (also for connecting an assistant to the MCP server) are included in the Pro plan, in both sizes (€19/month for 200 minutes, €49 for 1,000 and up to 10 people). For volumes or terms beyond that there's Enterprise, on request.