MCP Datastore Server
Related Servers
Alternatives to MCP Datastore Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAn 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-
- FlicenseNot gradedqualityDmaintenanceAn MCP (Multi-Agent Conversation Protocol) Server providing natural language access to Google's Cloud Datastore services through the v1beta1 API.-
- AlicenseDqualityDmaintenanceAn MCP server that enables querying and interacting with Google Cloud services including Logging, Spanner, Monitoring, and Cloud Trace through natural language.17260 npm1MIT

MCP Marketing Analyticsofficial
FlicenseAqualityBmaintenanceA minimal MCP server for marketing analytics data discovery and querying, supporting Google Ads integration with mock fallback and real API access.5-- AlicenseNot gradedqualityAmaintenanceA 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
- AlicenseAqualityCmaintenanceA 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.6MIT
TDQS
Scored across 5 tools
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.
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.
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.
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.