Documentation tools

The Bitmovin MCP server exposes Bitmovin's developer documentation and SDK example repositories as tools your AI client can call. Ask questions about our products, APIs, and SDKs from inside Claude, ChatGPT, Cursor, Claude Code, Windsurf, or anywhere else MCP is supported.

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

Documentation tools serve only public documentation and public GitHub sample repositories, so they work regardless of what your Bitmovin account has access to.

Tools

Tool	What it does
`general_docs_ask_bitmovin_docs`	Answers questions about Bitmovin products, APIs, codecs, streaming concepts, and player/encoding/analytics behavior, grounded in the developer documentation.
`general_docs_fetch_docs_page`	Retrieves a specific documentation page in full, for when you want the whole page rather than an answer.
`general_docs_search_bitmovin_sdk_examples`	Finds runnable code samples across Bitmovin's public Player and Encoding SDK example repos on GitHub.

What's indexed

developer.bitmovin.com — the full developer portal (Encoding, Playback, Analytics, Stream Lab, CDN).
cdn.bitmovin.com/player/* — Player SDK reference documentation.
Public Bitmovin SDK example repositories on GitHub.

Example prompts

"How do I configure Widevine DRM on the Bitmovin Web Player? Link me to the relevant docs."
"Show me a Java example that creates a VOD encoding with HLS and DASH outputs."
"What are all the supported codecs for live encoding today?"
"Find an iOS SDK sample that uses offline playback."
"Explain the difference between Per-Title and 3-Pass encoding, with a link to the docs."

Notes

The MCP server does not include a model — your MCP client's model does the reasoning. Costs, rate limits, and privacy follow your client's policies.
Answers cite the source page on developer.bitmovin.com or the GitHub sample file so you can jump to the original.
These tools are stateless; they do not retain your queries.