Skip to main content
Glama
qybbs

@qybbs/custom-bigquery-mcp

by qybbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @qybbs/custom-bigquery-mcp

No user-submitted related servers found.

    Related Servers

    • BigQuery-MCP

      Wayne9701
      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

    • BigQuery MCP Server

      amenke-lang
      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.
      -

    • GCP BigQuery MCP Server

      roymani06
      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.
      -

    • BigQuery MCP Server

      pvoo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to explore BigQuery datasets and tables, run safe read-only queries, and optionally perform vector search using BigQuery embeddings.
      152 PyPI
      10
      MIT

    • dbt-agents

      the-datastrategist
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to inspect, query, test, and safely fix dbt projects and BigQuery warehouses under policy-enforced controls, with read-only direct queries and dbt-only allowlisted writes.
      Apache 2.0

    • bigquery-mcp

      aicayzer
      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
    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

    A3.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    The five tools have largely distinct roles: listing, searching, describing, estimating, and executing. However, search_allowed_tables returns schema and partitioning details that overlap with describe_table, and list_allowed_tables overlaps with search_allowed_tables for table discovery. Descriptions clarify the differences, so confusion is limited.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (list_allowed_tables, describe_table, estimate_query_cost, execute_readonly_query, search_allowed_tables). Minor modifiers like 'allowed' and 'readonly' are used consistently and do not break the pattern.

    Tool Count5/5

    Five tools are well-scoped for a read-only BigQuery querying server, covering discovery, schema inspection, cost estimation, and execution. No tool feels redundant or missing, making the count appropriate.

    Completeness5/5

    The surface covers the full read-only query lifecycle: discovering allowed tables (list/search), understanding their schemas (describe), estimating cost, and executing queries. No obvious gaps exist for the stated purpose, though bulk schema retrieval could be slightly more efficient.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources