Skip to main content
Glama
johnreitano

MCP Datastore Server

by johnreitano

Related Servers

Alternatives to MCP Datastore Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      An MCP server that enables interaction with Google Firestore in Datastore mode for entity management and querying. It provides tools for CRUD operations, aggregation queries, and transaction execution within Google Cloud projects.
      11
      -
    • F
      license
      A
      quality
      B
      maintenance
      A minimal MCP server for marketing analytics data discovery and querying, supporting Google Ads integration with mock fallback and real API access.
      5
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP server for querying telemetry data from configurable backends. Provides tools to list sources, describe schemas, run bounded queries, and compute aggregates.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A Python MCP server that retrieves and caches BigQuery metadata (datasets, tables, columns) and enables secure SQL query execution with cost control, file export, and keyword search.
      6
      MIT

    TDQS

    B3.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have distinct purposes, but datastore_filter and datastore_query overlap significantly in functionality, which could cause confusion. The other tools (count, get, list_kinds) are clearly differentiated, but the boundary between filtering and querying is ambiguous.

    Naming Consistency5/5

    All tool names follow a consistent datastore_verb_noun pattern with snake_case, making them predictable and easy to understand. The naming convention is uniform across all five tools, with no deviations in style or structure.

    Tool Count4/5

    Five tools is a reasonable number for a datastore server, providing core operations like count, get, list, filter, and query. It's slightly lean but covers essential functions without being overwhelming, though it might benefit from additional CRUD operations for completeness.

    Completeness3/5

    The toolset includes read operations (get, filter, query, count, list) but lacks create, update, and delete tools, which are fundamental for a datastore's lifecycle. This gap limits agents to querying and reading data without the ability to modify it, making the surface notably incomplete for full datastore management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues