getAvailableMetrics — Bitmovin Observability MCP MCP Tool
getAvailableMetrics
(get available metrics) is one of 11 tools on the
Bitmovin Observability MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call getAvailableMetrics from your client
- Claude Code Bitmovin Observability MCP getAvailableMetrics run in your project directory
- Claude Desktop Bitmovin Observability MCP getAvailableMetrics ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Bitmovin Observability MCP getAvailableMetrics ~/.cursor/mcp.json
- VS Code Bitmovin Observability MCP getAvailableMetrics .vscode/mcp.json
- Zed Bitmovin Observability MCP getAvailableMetrics ~/.config/zed/settings.json
- Windsurf Bitmovin Observability MCP getAvailableMetrics ~/.codeium/windsurf/mcp_config.json
- Cline Bitmovin Observability MCP getAvailableMetrics ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Bitmovin Observability MCP getAvailableMetrics ~/.gemini/settings.json
- Grok Bitmovin Observability MCP getAvailableMetrics .mcp.json (in your project root)
- ChatGPT Bitmovin Observability MCP getAvailableMetrics Settings → Connectors → Advanced → Developer mode
- Claude.ai Bitmovin Observability MCP getAvailableMetrics Settings → Connectors → Add custom connector
- LangChain Bitmovin Observability MCP getAvailableMetrics pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http analytics-mcp https://analytics.mcp.bitmovin.comOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.