Skip to main content
Glama
gotalab

BigQuery Analysis MCP Server

by gotalab

Related Servers

Alternatives to BigQuery Analysis MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A read-only BigQuery MCP server with auto-LIMIT injection, dry-run cost guard, and ADC authentication. Allows safe SQL querying of BigQuery by LLMs without risk of data modification or unexpected costs.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for secure BigQuery access across multiple Google Cloud projects, enabling querying, schema exploration, and data analysis with SQL validation and read-only controls.
      2
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A server that connects to PostgreSQL databases and provides tools for safely exploring schemas, running read-only SQL queries, and performing data analysis with pre-built templates.
      6
      425 npm
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables validation and dry-run analysis of BigQuery SQL queries without execution. Provides cost estimates, schema previews, and syntax validation for BigQuery queries.
      9
      30 PyPI
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for running read-only SQL queries across MySQL and PostgreSQL databases with safety guardrails, credentials stored outside source, and support for multiple databases.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A read-only, schema-aware MCP server that connects to SQL databases and provides tools for refining questions, browsing schema, validating, explaining, and running SELECT statements with safety guards.
      MIT

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools have mostly distinct roles: one validates only, the other executes with built-in validation. There is mild overlap since run_query_with_validation internally performs a dry run, so an agent might briefly hesitate, but the outcome differences (no execution vs. execution) make the choice clear.

    Naming Consistency4/5

    Both names use snake_case and start with an action verb, which is consistent. However, 'dry_run_query' is a compact noun-style phrase while 'run_query_with_validation' is a longer descriptive phrase, a minor stylistic deviation.

    Tool Count3/5

    Two tools is thin for a server framed as 'BigQuery Analysis' — analysis usually implies exploration beyond validate/execute. The pair is coherent but leaves the surface feeling minimal.

    Completeness2/5

    There is no way to discover datasets, tables, or schemas, and no tool to run queries that legitimately contain DML or exceed 1 TB. Agents doing real analysis will hit dead ends when they need metadata or unrestricted execution.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues