List your agent

MCP Tools · find what your AI agent can connect to

358,804 tools from 21,355 MCP servers that answered our robot · tested every day · how we test

6 tools for “query postgres” in data-analysis · best match first · at most 3 per server

  1. queryGroupByworks without a keyofficial

    query metric grouped by categories. Queries resolve against API metric keywords, which can differ from a metric's common name — 'plays', for example, is 'impression_id'. The 'searchMetrics' tool resolves a keyword cheaply; 'getAvailableMetr

    on Bitmovin Observability MCP · 11 tools100% available over 30 dayschecked 15 h ago#data-analysis#debugging
  2. queryworks without a keyofficial

    Query a metric over a time range (start/end) for a license as a TIME SERIES — always renders a chart. Use this for trends and license-wide analytics over a period (e.g. 'last week', 'last 30 days', 'yesterday'). Bucket size is chosen automa

    on Bitmovin Observability MCP · 11 tools100% available over 30 dayschecked 15 h ago#data-analysis#debugging
  3. run_sqlworks without a keyofficial

    Run a read-only VinktarQL SELECT over the project's `events` table, for anything query_trends, query_funnel and query_retention cannot express; start with those, since what they run is what a board panel should be. A ClickHouse-flavoured su

    on Vinktar · 31 tools100% available over 30 dayschecked 37 h ago#data-analysis#debugging
  4. queryTotalworks without a keyofficial

    Get an aggregated value (one number) for a metric over a time range — no chart, no time bucketing. Can fetch SEVERAL metrics in one call: pass an array to `metric` to get one value per metric (e.g. the ad completion funnel), instead of call

    on Bitmovin Observability MCP · 11 tools100% available over 30 dayschecked 15 h ago#data-analysis#debugging
  5. query_funnelworks without a keyofficial

    Conversion through an ordered sequence of events (e.g. view_pricing → start_checkout → purchase): how many entered, how many reached each step, where they dropped, how long converting took, optionally by segment.

    on Vinktar · 31 tools100% available over 30 dayschecked 37 h ago#data-analysis#debugging
  6. query_retentionworks without a keyofficial

    Cohort retention: users who did targetEvent in a period form a cohort, and the table shows what share of each cohort did returningEvent in each later period. Use it for "do people come back" and "did retention improve after the change".

    on Vinktar · 31 tools100% available over 30 dayschecked 37 h ago#data-analysis#debugging