Cassandra MCP
Related Servers
Alternatives to Cassandra MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables interaction with Cassandra/Scylla databases via CQL, supporting read-only and unrestricted read/write operations through MCP tools.-
- 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.-
- FlicenseAqualityCmaintenanceSecurity-hardened, read-only MySQL MCP server that enables safe, read-only access to MySQL databases for running SELECT queries, exploring schemas, and sampling data via MCP clients.9-
- AlicenseAqualityCmaintenanceEnables MCP clients to securely query databases, list tables, inspect table schemas, and test connections across Oracle, SQL Server, MySQL, PostgreSQL, and SQLite using read-only SQL tools.4MIT
- AlicenseAqualityAmaintenanceEnables MCP clients to inspect Google Play releases, reviews, Android vitals, and scoped bulk reports, and to prepare explicitly authorized changes using locally supplied service-account credentials. Reads are default, while optional writes and sensitive reads require explicit configuration and single-use execution.413169 PyPIAGPL 3.0
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.