Encoding tools

The Bitmovin MCP Server gives your AI client read-only access to your Bitmovin encodings, both VOD and live. Ask questions like "list my encodings from the past week", "why did encoding X fail?" or "is my live channel healthy right now?", and get answers built from our Encoding APIs and event logs.

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

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.
`encoding_get_encodings`	Lists your VOD and live encodings, newest first, with filters
`encoding_get_encoding_overview`	Shows everything about one encoding in a single call, to answer what happened to it
`encoding_get_encoding_ladder`	Shows the rendition ladder of one encoding, so you can check what was actually encoded
`encoding_get_encoding_deliverables`	Shows where one encoding's output went: its muxings (such as fMP4, TS, MP4 or CMAF) and outputs
`encoding_get_codec_configurations`	Shows codec configuration settings
`encoding_get_encoding_templates`	Lists your stored encoding templates, with name, description and type (VOD or live)
`encoding_get_live_encoding_health`	Checks whether a live channel is healthy right now, including its ingest status
`encoding_get_live_events`	Shows the event history of a live encoding: connects, disconnects and reconnects
`encoding_get_live_stream_statistics`	Shows per-minute ingest statistics for a live encoding
`encoding_get_live_srt_statistics`	Shows SRT link statistics for a live encoding with an SRT input
`encoding_get_live_standby_pools`	Shows your live standby pools and their headroom, so you know if new channels can start
`encoding_get_daily_statistics`	Shows your encoding usage day by day
`encoding_get_encoding_statistics`	Shows usage per encoding between two dates, for VOD or live encodings
`encoding_get_error_definitions`	Looks up Bitmovin's encoding error codes: category, message and description

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

VOD encodings

"List my encodings from the past week and flag any that failed."
"Why did encoding [encoding ID] fail, and what does the error code mean?"
"Show me the rendition ladder of my latest encoding and where the output was written."
"Summarize encoding activity in the last 24 hours: total count, status breakdown and any errors."

Live encodings

"List my five most recent live encodings and flag any that didn't reach RUNNING."
"Is my live encoding [encoding ID] healthy right now? Show any disconnects in the last hour."
"Why did encoding [encoding ID] take so long to start?"
"Which of my encodings from yesterday fell back to an alternative cloud region?"
"Show the SRT statistics for my live encoding [encoding ID] over the last 30 minutes."
"Do my standby pools have enough headroom to start two more live channels?"

Usage and templates

"How many encoding minutes did we use each day last month?"
"Which of my encodings used the most minutes last week?"
"List my encoding templates and what each one is for."

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.