Skip to main content
Glama
takada-at

bq_mcp_server

by takada-at
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to bq_mcp_server

No user-submitted related servers found.

    Related Servers

    • MCP BigQuery Server

      rodneyelmore
      A
      license
      Not graded
      quality
      D
      maintenance
      Production-ready MCP server for BigQuery that translates natural language questions to SQL, executes queries securely, and delivers results via stdio or HTTP for integration with GitHub Copilot, Power BI, and web applications.
      689 npm
      MIT

    • 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

    • GCP BigQuery MCP Server

      erayguner
      A
      license
      Not graded
      quality
      C
      maintenance
      Enterprise-grade MCP server for Google Cloud BigQuery with keyless Workload Identity Federation authentication, enabling secure SQL query execution, dataset management, and schema inspection with comprehensive audit logging and encryption.
      MIT

    • bq-readonly-mcp

      mariadb-RupeshBiswas
      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
    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.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: checking query cost, executing queries, listing datasets/tables, saving results, and searching metadata. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., 'check_query_scan_amount', 'execute_query', 'get_datasets'), making them predictable and easy to distinguish.

    Tool Count5/5

    With 6 tools, the server is well-scoped for BigQuery query and metadata operations. Each tool serves a necessary function without redundancy or bloat.

    Completeness5/5

    The tool set covers all core workflows for BigQuery exploration: listing resources, checking query cost, executing queries, saving results, and searching metadata. No obvious gaps are present for this domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources