MCP · REST · OpenAPI · Receipts

Your agent has the brains. Everpop is the hands.

The clipping tool an AI agent can drive end-to-end: upload the file, clip the best moments, publish to the user's own channel, and read real measured results — without ever leaving the API.

Official YouTube APIs end-to-end · the user's own file · receipts, not vibes

The whole loop, by API

1.Upload the file

POST /api/v1/videos/upload → presigned PUT → /complete. Your agent delivers the bytes itself — no human detour. Auto-clips on completion for active plans.

2.Clip anything

POST /api/v1/clip with an optional natural-language steer ('the most surprising moment'). Or generate a Short from a bare prompt.

3.Publish — with consent

POST /api/v1/publish posts to the user's own channel via YouTube's official API. Publishing always requires the human's explicit go-ahead. No spray, no spam.

4.Read the receipts

GET /api/v1/receipts — real YouTube Analytics at 48h and 7d per clip. Tamper-evident numbers your agent can reason about and report.

Three ways in

MCP connector

13 tools over Streamable HTTP — generate, upload, clip, publish, receipts, campaigns. Add it to Claude (or any MCP client) in one paste.

https://everpop.app/api/mcp/mcp?key=epk_…

REST + OpenAPI

Plain JSON over HTTPS with a machine-readable schema — point a codegen or a GPT Action at it and go.

https://everpop.app/openapi.json

Agent guide

One markdown file teaches the whole loop — auth, endpoints, gotchas, and the exact curl for every step.

https://everpop.app/skill.md

Auth is one per-user API key (Bearer epk_…) — created by the human in Settings → API keys, read-only or full scope, revocable anytime.

Install in your tools

One click for Cursor, or a copy-paste config for any MCP client.

➕ Add Everpop to Cursor

One click installs the connector; Cursor runs the OAuth sign-in. Other tools — copy a config below.

Cursor / Windsurf / Cline

~/.cursor/mcp.json (or the app's MCP settings)

{
  "mcpServers": {
    "everpop": {
      "url": "https://everpop.app/api/mcp/mcp?key=epk_YOUR_KEY"
    }
  }
}

VS Code (Copilot MCP)

.vscode/mcp.json

{
  "servers": {
    "everpop": {
      "type": "http",
      "url": "https://everpop.app/api/mcp/mcp?key=epk_YOUR_KEY"
    }
  }
}

Claude Desktop / Code

claude_desktop_config.json — or just paste the URL as a custom connector (OAuth, no key needed)

{
  "mcpServers": {
    "everpop": {
      "url": "https://everpop.app/api/mcp/mcp"
    }
  }
}

Replace epk_YOUR_KEY with a key from Settings → API keys. Clients that support MCP OAuth (Claude, Cursor) can use the bare URL and sign in instead.

Why agents pick Everpop

Deterministic contracts. Every error is JSON with a stable code — a 422 upload_required tells your agent exactly what to do next, in the message.
Safe by construction. Ingestion is the user's own file over official APIs — an agent can't accidentally endanger the channel it's helping. Publishing requires explicit human consent, always.
Closed feedback loop. Receipts turn publishing into data your agent can learn from: clip → publish → measure → clip better.
Idempotent everything. Retries never double-render or double-post — built for at-least-once agent loops.

Wire it up in five minutes

Read skill.md, create a key, and your agent is clipping. Or paste the MCP connector into Claude and just ask.