Astra DB MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASTRA_DB_KEYSPACE | No | The keyspace to connect to (optional, defaults to the keyspace configured in the Astra DB library, typically 'default_keyspace') | |
| ASTRA_DB_API_ENDPOINT | Yes | Your Astra DB API Endpoint | |
| ASTRA_DB_APPLICATION_TOKEN | Yes | Your Astra DB Application Token |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| GetCollectionsB | Get all collections in the Astra DB database |
| CreateCollectionC | Create a new collection in the database |
| UpdateCollectionC | Update an existing collection in the database |
| DeleteCollectionC | Delete a collection from the database |
| ListRecordsC | List records from a collection in the database |
| GetRecordC | Get a specific record from a collection by ID |
| CreateRecordC | Create a new record in a collection |
| UpdateRecordC | Update an existing record in a collection |
| DeleteRecordC | Delete a record from a collection |
| FindRecordC | Find records in a collection by field value |
| BulkCreateRecordsC | Create multiple records in a collection at once |
| BulkUpdateRecordsC | Update multiple records in a collection at once |
| BulkDeleteRecordsC | Delete multiple records from a collection at once |
| OpenBrowserC | Open a web browser to a specific URL |
| EstimateDocumentCountA | Estimate the number of documents in a collection using a fast, approximate count method |
| HelpAddToClientB | Help the user add the Astra DB client to their MCP client |
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 16 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are well-organized around specific resources (collections, records) and actions (create, get, update, delete, list, find, estimate), and even bulk operations are clearly separated from single operations. There is no overlap that would cause misselection.
Tool names follow a highly consistent verb_noun pattern throughout, using PascalCase for readability. All tools start with an action verb (e.g., Create, Delete, Get, Update) followed by a noun (e.g., Record, Collection), with only minor variations like 'HelpAddToClient' and 'OpenBrowser' still fitting the pattern. There are no mixed conventions or chaotic naming.
With 16 tools, this is well-scoped for a database server covering collections and records. Each tool earns its place by providing comprehensive CRUD operations, bulk handling, and utility functions, without being excessive or thin for the domain. The count supports a complete workflow without overwhelming an agent.
The tool surface offers complete CRUD/lifecycle coverage for both collections and records, including bulk operations, listing, finding, and estimation. There are no obvious gaps; agents can perform all essential database tasks from creation to deletion, with added utilities like HelpAddToClient and OpenBrowser for setup and navigation.