Cassandra MCP
Related Servers
Alternatives to Cassandra MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables agents to run SELECT-only queries and inspect table metadata against configured databases via MCP Proxy, with timeouts, row and byte caps, and audit logging.MIT
- FlicenseNot gradedqualityBmaintenanceEnables interaction with Cassandra/Scylla databases via CQL, supporting read-only and unrestricted read/write operations through MCP tools.-
- AlicenseBqualityCmaintenanceEnables read-only analysis of allowlisted Google Analytics 4, Google Tag Manager, and Google Ads resources via local stdio MCP tools for reporting, admin reads, GTM container inspection, and GAQL queries.5MIT
- FlicenseAqualityBmaintenanceEnables MCP clients to safely inspect and query an explicitly allowlisted subset of a Postgres database through four read-only tools: a readiness check, table listing, column description, and typed row selection with filters, ordering, and paging. It runs over stdio for local clients or Streamable HTTP for separately managed ones, with bound parameters, bounded reads, and read-only transactions.4-
- FlicenseNot gradedqualityCmaintenanceEnables read-only access to explicitly approved local and remote filesystems, including inspecting Git repositories and querying SQLite and DuckDB databases, with root administration kept separate from MCP.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to inspect schemas, sample rows, run safe read-only SELECT queries, plan joins, and analyze columns across SQLite and PostgreSQL with row limits, access controls, and sensitive-column masking.MIT
TDQS
Scored across 3 tools
Each tool targets a clearly distinct action on the Cassandra schema/data model: enumerate tables, inspect a table's structure, and read rows. There is no overlap or plausible confusion between list/describe/read.
All three follow a clean verb_noun snake_case pattern (list_tables, describe_table, read_partition). The only nit is inconsistent pluralization (tables plural vs. table/partition singular), but the convention is still predictable.
Three tools is lean but defensible for a deliberately read-only, safety-scoped server. It is on the thin side and would feel limiting if more discovery/read capability were expected.
The read-only surface covers basic discovery and full-partition reads, but there is no keyspace enumeration, no clustering-key/range reads, and no write operations. Some gaps are intentional safety choices, but agents will hit dead ends for anything beyond full-partition lookups.