MCP server
Put BeemMeUp inside your coding agent.
The BeemMeUp MCP server hands your agent the tools the app runs on: filter-graph visualisation, command linting, manifest inspection and your own media. Connect once, then ask in plain language.
6
tools
0
keys to paste
Free
on every plan
Claude Code
Let’s visualize this with BeemMeUp MCP — the overlay pass drops frames on 4K sources.
beemmeup.visualize_graphCalling
{
"command": "ffmpeg -i cam.mp4 -i logo.png -filter_complex
\"[0:v][1:v]overlay=W-w-20:20[o];[o]scale=1920:1080[v]\"
-c:v libx264 -crf 23 out.mp4"
}What the agent gets
Six tools. You choose which ones are granted when you authorize, and you can revoke any client from your account.
Visualize filter graphs
graph.visualizeTurn an FFMPEG command into a node graph with warnings.Explain and lint commands
command.explainFlag wasted passes, bad flags and unreachable filters.Inspect HLS and DASH manifests
manifest.inspectRead a playlist URL and report variants, segments and gaps.Read your Media Library
library.readList file names, durations and codecs. Never the files themselves.Run encodes in your workspaceWrite
encode.runStart a local encode on your machine, then check on it with get_job.Save results to your accountWrite
results.writeWrite graphs and reports back into your saved pipelines.Connect in one step
There is no API key to paste. Add the server, and the first call opens your browser to authorize with your BeemMeUp account.
terminal
claude mcp add --transport http beemmeup https://www.beemmeup.io/mcp/v1
Run this once in any project. The transport is HTTP, so there is nothing to install locally.
Your files never leave your machineThe server sees commands, manifests and metadata — not media.
Scopes you pickGrant read-only tools and leave encode and write access off.
One token per clientEvery agent holds its own token. Revoke one without touching the rest.