Skip to main content
Glama
flin-bigquery-mcp

flin-bigquery-mcp

by flin-agency

Related Servers

Alternatives to flin-bigquery-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables read-only interaction with Google BigQuery, including SQL queries, dataset/table listing, schema retrieval, table preview, and metadata access via service account authentication.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Google BigQuery, allowing users to list tables, inspect metadata, and run SELECT queries with enforced row and byte limits.
      Apache 2.0
    • A
      license
      B
      quality
      C
      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
      60 PyPI
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables safe read-only access to allowlisted Google Cloud BigQuery tables with schema inspection, keyword search, cost estimation, and strict FinOps guardrails. It supports cross-project billing and limits queries by byte caps and row limits.
      5
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables secure read-only interaction with Google BigQuery through natural language, including listing datasets, listing tables, retrieving metadata, and executing queries with cost controls.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to browse BigQuery datasets and table metadata, run capped read-only SQL with cost estimates and dry runs, trace upstream/downstream table lineage, and fetch Dataplex data-quality scan results over a streamable-http endpoint on Cloud Run.
      MIT

    TDQS

    A3.6/5.0

    Scored across 11 tools

    Disambiguation3/5

    The browse/inspect tools (list_projects, list_datasets, get_dataset, list_tables, get_table, preview_table) and the query trio (dry_run_query, run_query, get_query_results) are cleanly separated. However, health_check and connection_status both describe purely local configuration checks that never contact Google, making them near-duplicates an agent could easily pick the wrong one of. The distinction (ADC probing vs. token validity claims) is subtle and buried in long prose.

    Naming Consistency4/5

    Strong verb_noun snake_case pattern throughout: list_projects, get_dataset, preview_table, dry_run_query, get_query_results. The only deviations are the two status-style names health_check and connection_status, which break the verb-first convention but remain readable and idiomatic.

    Tool Count5/5

    Eleven tools is well within the sweet spot for a metadata-browse plus query-execution server. Each tool maps to a distinct step in the navigation/query workflow with little filler.

    Completeness4/5

    The explore-then-query lifecycle is well covered: projects → datasets → tables → schema/preview → dry run → execute → poll/paginate results. The notable gap is the absence of any cancellation or job-listing operation, so a runaway or expensive query has no abort path; agents can otherwise work within the read-only surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues