Encoding tools

The Bitmovin MCP server gives your AI client read-only access to your Bitmovin encodings. Ask natural-language questions like "list my encodings from the past week", "why did encoding X fail?", or "which encodings hit our region-fallback path yesterday?" — and get back grounded answers composed from our encoding APIs and event logs.

These are the encoding_* tools on mcp.bitmovin.com. To connect, see AI at Bitmovin.

Encoding tools see only the encodings your credential has access to. Where possible, connect with a scoped, least-privilege API key, or use OAuth so access follows your own Bitmovin permissions.

Tools

Tool	What it does
`encoding_ask_bitmovin_encoding`	Answers questions about your encodings — list with filters, inspect detail, explain failures, summarize recent activity.

Behind that single tool sits an agent that combines the Encoding REST API with event-log data. That combination is what makes it useful for diagnosing live encoding issues — VM provisioning delays, region fallbacks, RTMP connection events, and similar.

Example prompts

"List my five most recent live encodings and flag any that didn't reach RUNNING."
"Why did encoding 4c314e8d-54b6-4b89-8cd5-204abc5c6df5 take so long to start?"
"Summarize encoding activity in the last 24 hours — total count, status breakdown, and any errors."
"Which of my encodings from yesterday fell back to an alternative cloud region?"
"Give me the error message and the last 10 event-log entries for encoding X."

Notes

The MCP server does not include a model; your MCP client's model reasons over the tool responses.
Calls count against your normal Bitmovin API rate limits.
These tools are read-oriented — they do not create, modify, or delete encodings.
Tool invocations are traced via Langfuse so we can detect regressions and improve quality over time. Your API key and tool arguments are not retained in those traces beyond standard operational logging.