Reference and support¶
Technical guides¶
| Guide | What it covers |
|---|---|
| Tools | Arguments, outputs, resources, prompts, and error codes |
| Configuration | Credential precedence, profiles, project settings, and read-only mode |
| Troubleshooting | Connection, permission, and client problems |
| Hosted connection | HTTP transport, OAuth, and self-hosting |
| IBM Bob | Bundle installation and supported workflows |
| Security | Confirmation, credential handling, and access boundaries |
These guides live with the source so implementation and reference changes can be reviewed together.
Something is not working¶
- Run
npx -y @erichare/astra-mcp doctorin the affected project. - Check which credential source and database are selected. Never include tokens in a report.
- Confirm the plugin and MCP server are enabled, and restart the agent after installation changes.
- Open an issue with the client version, plugin version, redacted error, and the smallest reproducible example.
Data and privacy¶
The local server connects to Astra with your credentials. Database content returned by tools goes to your chosen agent under that provider's terms. A local launcher does not mean a remote database query stays on your computer. Hosted deployments have their own connection and credential handling.
Read the privacy notice and terms.
Distribution status¶
Version 2.1.0 is published. Claude Code and Codex can install from the repository's community marketplaces. The npm server remains @erichare/astra-mcp; the native plugin identifier remains astra-db@astra-db-marketplace.
Official directory submission is a separate process. Maintainer publishing guidance and the directory update record document the distinction between the local package and hosted submission requirements. No official approval is claimed here.
JEStats Astra DB Plugin is community maintained and is not affiliated with or endorsed by DataStax or IBM. Their names identify compatibility.