Astradb

Created By
datastaxa year ago
Overview

What is Astra DB MCP?

Astra DB MCP is a Model Context Protocol server designed for interacting with Astra DB, enhancing the capabilities of Large Language Models (LLMs) by enabling them to function as agents that can interact with external systems.

How to use Astra DB MCP?

To use Astra DB MCP, you need to have a running Astra DB database. After creating a free database, you will obtain an Astra DB Application Token and API Endpoint. You can then add the MCP server to your client (e.g., Claude Desktop or Cursor) by configuring the necessary settings as outlined in the documentation.

Key features of Astra DB MCP?

  • Interacts with Astra DB to manage collections and records.
  • Provides tools for creating, updating, and deleting collections and records.
  • Supports bulk operations for managing multiple records at once.
  • Offers a web browser interface for authentication and setup.

Use cases of Astra DB MCP?

  1. Managing collections in Astra DB for data organization.
  2. Performing bulk operations for efficient data handling.
  3. Integrating with LLMs to enhance data interaction capabilities.

FAQ from Astra DB MCP?

  • What do I need to get started?

You need an Astra DB database, an application token, and the API endpoint.

  • Can I use Astra DB MCP with any client?

Yes, it can be integrated with various clients like Claude Desktop and Cursor.

  • What operations can I perform with Astra DB MCP?

You can create, read, update, and delete collections and records, as well as perform bulk operations.

Server Config

{
  "mcpServers": {
    "astra-db-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@datastax/astra-db-mcp"
      ],
      "env": {
        "ASTRA_DB_APPLICATION_TOKEN": "your_astra_db_token",
        "ASTRA_DB_API_ENDPOINT": "your_astra_db_endpoint"
      }
    }
  }
}
Project Info
Hosted
Created At
a year ago
Updated At
a year ago
Author Name
datastax
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago