available licenses — Bitmovin Observability MCP MCP Resource
available licenses
is one of 6 resources on the
Bitmovin Observability MCP
MCP server. Connect the server and your client can attach it as context.
by client
How to attach available licenses from your client
- Claude Code Bitmovin Observability MCP Resource/available licenses run in your project directory
- Claude Desktop Bitmovin Observability MCP Resource/available licenses ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Bitmovin Observability MCP Resource/available licenses ~/.cursor/mcp.json
- VS Code Bitmovin Observability MCP Resource/available licenses .vscode/mcp.json
- Zed Bitmovin Observability MCP Resource/available licenses ~/.config/zed/settings.json
- Windsurf Bitmovin Observability MCP Resource/available licenses ~/.codeium/windsurf/mcp_config.json
- Cline Bitmovin Observability MCP Resource/available licenses ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Bitmovin Observability MCP Resource/available licenses ~/.gemini/settings.json
- Grok Bitmovin Observability MCP Resource/available licenses .mcp.json (in your project root)
- ChatGPT Bitmovin Observability MCP Resource/available licenses Settings → Connectors → Advanced → Developer mode
- Claude.ai Bitmovin Observability MCP Resource/available licenses Settings → Connectors → Add custom connector
- LangChain Bitmovin Observability MCP Resource/available licenses pip install langchain-mcp-adapters
Other resources on this server
Bitmovin Observability MCP also offers 3 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.