MCP Datastore Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CLOUD_PROJECT | Yes | Your Google Cloud project ID | |
| GOOGLE_APPLICATION_CREDENTIALS | Yes | Path to your service account JSON key file |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| datastore_getC | Get an entity by kind and key from Datastore |
| datastore_insertC | Insert a new entity into Datastore |
| datastore_updateC | Update an existing entity in Datastore |
| datastore_upsertC | Insert or update an entity in Datastore (upsert operation) |
| datastore_deleteC | Delete an entity from Datastore |
| datastore_queryC | Query entities from Datastore with optional filters, ordering, and pagination |
| datastore_runAggregationQueryC | Run an aggregation query (count, sum, avg) on Datastore entities |
| datastore_allocateIdsC | Allocate IDs for incomplete keys |
| datastore_createKeyC | Create a complete or incomplete key |
| datastore_runInTransactionB | Execute multiple operations within a transaction |
| datastore_listKindsB | List all entity kinds (types) in the Datastore by querying the kind metadata |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Every tool has a clearly distinct purpose with no ambiguity. Each targets a specific Datastore operation (e.g., get vs. query vs. runAggregationQuery), and even similar-sounding tools like insert, update, and upsert are clearly differentiated in their descriptions.
All tools follow a consistent 'datastore_verbNoun' pattern with snake_case throughout. The naming is predictable and readable, making it easy to understand each tool's function at a glance.
With 11 tools, this server is well-scoped for Datastore operations. Each tool earns its place by covering essential CRUD, querying, transaction, and metadata functions without being overwhelming or sparse.
The toolset provides complete coverage for Datastore operations, including key management (allocateIds, createKey), CRUD (insert, get, update, delete, upsert), querying (query, runAggregationQuery), transactions (runInTransaction), and metadata (listKinds). There are no obvious gaps that would hinder agent workflows.