Remove green screens from your AI client

Connect the Zapmatte green screen remover through the Model Context Protocol (MCP). Point your client at a clip, approve the credit cost, and get back ProRes 4444 with alpha, a transparent WebM and an alpha matte, or an MP4 on a solid colour.

Same processing as the website · Your existing credits · Failed jobs refunded automatically

Connect

Use a client that supports remote MCP over Streamable HTTP with a custom Authorization header, such as Claude Code or Cursor. Server URL:

https://zapmatte.com/api/mcp

Your MCP key

A key lets your AI client upload videos, spend your Zapmatte credits on green screen removal, and read your balance and results. It expires after 30 days, and you can have up to five at once. Only give it to clients you trust.

Loading account…

Client configuration

Replace YOUR_ZAPMATTE_KEY with your key in your client's private MCP settings. This example uses the mcpServers format from Cursor; other clients may differ.

{
  "mcpServers": {
    "zapmatte": {
      "url": "https://zapmatte.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ZAPMATTE_KEY"
      }
    }
  }
}

Claude Code:

claude mcp add --transport http zapmatte https://zapmatte.com/api/mcp \
  --header "Authorization: Bearer YOUR_ZAPMATTE_KEY"

Keys are personal Bearer keys, not OAuth, so clients that only support OAuth connectors can't sign in. Listing options and estimating cost work without a key.

Six tools

list_removal_options
Quality options, credits per second, limits and the files a job returns. No key needed.
estimate_removal_cost
The exact credit cost for a video of a given length. No key needed.
get_credit_balance
The credits left in your Zapmatte account.
create_upload
Screens 1-4 frames of the clip and returns a one-time URL to upload the video file to.
remove_green_screen
Starts the job on the uploaded video, transparent or on a solid colour.
get_removal_status
Follows the job and returns links to the ProRes, WebM, matte and preview files.

From clip to transparent video

  1. Your client lists the options, checks your balance and quotes the cost. You approve it.
  2. It grabs four frames from the clip, calls create_upload, and uploads the file to the URL it gets back.
  3. It starts remove_green_screen with a unique requestId and checks the job every few seconds.
  4. When it's done, it downloads the files you asked for.

Example: “Take ~/Videos/intro.mp4, remove the green screen with Zapmatte and save the ProRes file next to it. Tell me the cost first and wait for my OK.”

Working with video files

Video never passes through the chat. Your client needs access to the file (Claude Code, Cursor or any client with a shell) to read its length and size, extract four frames for screening and upload it. With ffmpeg and curl that looks like:

ffprobe -v error -show_entries format=duration:stream=width,height -of json intro.mp4
ffmpeg -ss 1 -i intro.mp4 -frames:v 1 -vf scale=640:-2 f1.jpg   # repeat for 4 points
# create_upload → { key, putUrl, contentType }
curl -T intro.mp4 -H "Content-Type: video/mp4" "<putUrl>"

Clips can be up to 3 minutes, 500 MB and 4K, shot on a green or blue screen.

Credits and results

There is no separate MCP plan. Jobs use the same credits, content rules and failure refunds as the website, and every finished video appears under My videos with its own page. Identical retries with the same requestId are recognised for 24 hours. If a submission times out, check My videos before trying again; a new requestId can start another paid job.