Skip to main content
Glama
krzko

Google Cloud MCP Server

by krzko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Google Cloud MCP Server

No user-submitted related servers found.

    Related Servers

    • Google Cloud MCP Server

      andyl25
      A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol server that connects to Google Cloud services, allowing users to query logs, interact with Spanner databases, and analyze monitoring metrics through natural language.
      78 npm
      MIT

    • GCP MCP

      eniayomi
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants like Claude to interact with Google Cloud Platform environments through natural language, allowing users to query and manage GCP resources during conversations.
      9
      1,740 npm
      200
      MIT

    • gcp-mcp-server

      LokiMCPUniverse
      F
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol server for Google Cloud Platform, enabling interaction with Resource Manager, Compute Engine, Cloud Storage, BigQuery, Pub/Sub, and Cloud Logging via natural language.
      3
      -

    • BigQuery MCP server

      LucasHild
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides access to BigQuery. This server enables LLMs to inspect database schemas and execute queries.
      130
      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

    C2.2/5.0

    Scored across 40 tools

    Disambiguation3/5

    Tools are separated by service prefix, but within services like logging and Spanner, multiple tools for querying logs or databases overlap in purpose. Additionally, many tools lack descriptions, increasing ambiguity.

    Naming Consistency5/5

    All tools follow a consistent pattern: 'gcp-{service}-{action}-{noun}' in snake_case. For example, gcp-billing-list-accounts, gcp-iam-get-project-policy. No mixing of styles.

    Tool Count3/5

    40 tools is high but not extreme for a multi-service server. However, several services have only 3 tools with missing descriptions, suggesting the count is inflated without full coverage.

    Completeness2/5

    Many services have significant gaps: error reporting, monitoring, profiler, and trace lack CRUD operations and detailed descriptions. Spanner is missing update/delete. Billing and logging are more complete, but overall surface is incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources