Public API and MCP server
Slicer opens a public REST API and an MCP server — make, edit and publish reels from your own code or through AI agents with an API token or OAuth.
Everything you do in Slicer by hand can now be done programmatically or handed to an AI agent.
Public API 1.0
A REST API at https://api.slicer.media/v1:
- Uploads — in parts, as a whole in one request, or from a public link.
- Montage and price — the price is always named before the start and confirmed explicitly; without confirmation no tokens are spent.
- Projects — status, stages, versions, picking a version, history, downloading the reel and its cover.
- Edits — operations on the reel's text, clips and elements, or replacing the document; the AI assistant and caption translation.
- Export and publishing — the file profile and publishing to connected social accounts.
- Webhooks — signed notifications about finished uploads, reels, exports and publications.
- An OpenAPI 3.1 specification, errors with clear codes, per-token rate limits, idempotency, cursor pagination.
App-only for now: buying packs, connecting social accounts, background removal, voice isolation, AI avatar, your own media and music in the editor — they will come in later API versions.
MCP server
The server at https://api.slicer.media/mcp connects to Claude, Claude Code, Cursor, VS Code, Codex, ChatGPT and other
clients: ask the agent to make a reel from files, edit it or publish it. Sign in through the browser (OAuth) or with an
API token. Paid tools require confirming the price, and each connection has a spending limit.
“For developers” in your profile
A new screen in the profile: API tokens with scopes, expiry and spending limits, connected apps, the MCP server address and webhooks.