available filters — Bitmovin Observability MCP MCP Resource

available filters 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 filters from your client

• Claude Code Bitmovin Observability MCP Resource/available filters run in your project directory
• Claude Desktop Bitmovin Observability MCP Resource/available filters ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Bitmovin Observability MCP Resource/available filters ~/.cursor/mcp.json
• VS Code Bitmovin Observability MCP Resource/available filters .vscode/mcp.json
• Zed Bitmovin Observability MCP Resource/available filters ~/.config/zed/settings.json
• Windsurf Bitmovin Observability MCP Resource/available filters ~/.codeium/windsurf/mcp_config.json
• Cline Bitmovin Observability MCP Resource/available filters ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Bitmovin Observability MCP Resource/available filters ~/.gemini/settings.json
• Grok Bitmovin Observability MCP Resource/available filters .mcp.json (in your project root)
• ChatGPT Bitmovin Observability MCP Resource/available filters Settings → Connectors → Advanced → Developer mode
• Claude.ai Bitmovin Observability MCP Resource/available filters Settings → Connectors → Add custom connector
• LangChain Bitmovin Observability MCP Resource/available filters pip install langchain-mcp-adapters

Other resources on this server

• Analytics Time-Series Chart
• Analytics Group-By Chart
• available metrics
• available licenses
• help

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.