mcp · handle cpr43_metabase_mcp · source page
zsh52013148087_metabase_mcp · job 92%Metabase Analytics Integration Server · job 92%Kyomi · job 81%metabase_server · job 93%agenticbi · job 73%metabase_ai_assistant · job 81%Looker Studio MCP · job 77%New Relic MCP Server · job 73%clicdata_mcp · job 74%Snowflake MCP Server · job 72%metaview_mcp · job 73%universal_db_mcp · job 80%ryanmaule_metabase_mcp · job 91%clearml_mcp · job 75%bigquery · job 71%gooddata_mcp_server · job 71%setoku · job 75%semanticops_mcp · job 73%mcp_metabase_server · job 85%db_mcp_server · job 77%alertmanager_mcp_server · job 71%AI for Database · job 78%DatabaseMcpServer · job 70%metabase_mcp_server · job 92%data-connector · job 73%Supabase MCP Server · job 76%ClickHouse MCP Server · job 73%AthenaHQ MCP Server · job 72%chartbrew_mcp_2 · job 70%Metabase MCP · job 83%Fluxito Community · job 75%DashThis MCP Connector · job 75%Yandex Metrika MCP Server · job 73%Power BI Fullstack MCP · job 72%MCP MongoDB Server · job 78%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series