No user-submitted related servers found.
Scored across 429 tools
The tool set has massive overlap: execute_query/execute_card/run_dashcard_query, move_cards_to_collection/bulk_move_cards, save_dashboard/create_dashboard/update_dashboard, and dozens of public/embed/preview query variants are nearly indistinguishable without deep context. An agent would frequently select the wrong tool.
A broad verb_noun pattern exists, but it is inconsistent across the set: run vs execute vs get, search_embed_dashboard_params vs get_embed_dashboard_param_values, enable_model_persistence vs persist_database_models, and odd verbs like dismiss_database_spinner and undo_pulse_unsubscribe break predictability.
429 tools is an extreme mismatch for an MCP server. Even for a comprehensive Metabase API wrapper, this volume overwhelms context windows and creates hundreds of redundant or near-duplicate entry points.
Metabase's major domains are covered extensively: cards, dashboards, databases, tables, fields, users, permissions, collections, actions, alerts, pulses, timelines, embedding, and x-rays. Minor gaps exist such as no create_alert, no delete_pulse, no unarchive_snippet, and no metric CRUD, but most workflows have no dead ends.