Skip to main content
Glama
im-voracity

metabase-mcp-python

by im-voracity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to metabase-mcp-python

No user-submitted related servers found.

    Related Servers

    • Metabase MCP Plus

      schachan
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to query databases, execute SQL, and manage Metabase resources like dashboards, cards, and collections through natural language.
      22
      MIT

    • Metabase MCP Server

      sazboxai
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Control Protocol server that enables AI assistants to interact with Metabase databases, allowing models to explore database schemas, retrieve metadata, visualize relationships, and execute actions.
      7
      -

    • @takeokunn/metabase-mcp

      takeokunn
      A
      license
      C
      quality
      B
      maintenance
      A Model Context Protocol server for Metabase that enables AI assistants to interact with Metabase instances, providing 418 tools across 58 categories for database, card, dashboard, collection, user, permissions, and more management.
      100
      6 npm
      2
      MIT

    • metabase-mcp

      livingroot
      A
      license
      Not graded
      quality
      B
      maintenance
      A TypeScript/Node.js MCP server that wraps the Metabase REST API, enabling AI agents to execute queries, explore schemas, and build dashboards through structured tool calls.
      29 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: database vs table vs card vs dashboard vs collection operations are well-separated. Even similar tools like get_table and get_table_data are distinct (metadata vs sample data).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, with clear verbs like get, list, execute, create, and search. No mixed conventions or ambiguous verbs.

    Tool Count4/5

    19 tools is on the higher end of appropriate for a Metabase server, covering databases, tables, cards, dashboards, collections, and querying. Slightly heavy but each tool provides distinct functionality.

    Completeness3/5

    The set covers reading and querying well, but lacks create/update/delete operations for cards and collections. Only dashboard creation exists, leaving obvious lifecycle gaps for analytical content.

    Maintenance

    ActivityNo data
    ResponsivenessUnresponsive

    Resources