AI Data MCP
Related Servers
Alternatives to AI Data MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to connect to and interact with MySQL, Redis, and MongoDB through a stdio MCP server, with unified data source discovery, read-only querying, and explicitly authorized write operations.MIT
- AlicenseBqualityBmaintenanceEnables agents to connect to and work with PostgreSQL, MySQL, Redis, SQLite, and MongoDB through a uniform tool surface for opening connections, running queries and commands, inspecting schemas, and managing documents.13844 npmMIT
- AlicenseAqualityCmaintenanceEnables MCP clients such as Codex to safely inspect a MySQL database over stdio by listing tables, describing schemas and indexes, and running only validated single read-only SELECT/CTE queries plus JSON EXPLAIN plans. Queries execute inside read-only transactions with strict AST-based rejection of writes, multi-statements, and other risky operations, and results come back as structured JSON.693 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to explore and query Postgres, MySQL, and BigQuery databases—listing schemas and tables, describing columns, sampling rows, running read-only SQL, and, when permitted, executing writes—with schema allowlists, hidden columns, response budgets, and audit logging. Runs on Node/Docker over stdio or Streamable HTTP, or as a Cloudflare Worker with OAuth and Hyperdrive.259 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to discover and query data federated across MySQL/MariaDB, PostgreSQL, ClickHouse, S3 and Kafka with SQL, exposing tools to list databases, schemas, tables and connections, describe columns, search objects, inspect table statistics, run EXPLAIN, and execute arbitrary statements. It runs locally over stdio against a PostgreSQL-wire endpoint and returns structured results or SQLSTATE-coded errors.8Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables agents to inspect and query local SQLite databases and, when write mode is enabled, perform inserts, updates, deletes, schema changes, and atomic transactions over stdio.1MIT
TDQS
Scored across 18 tools
Tools are cleanly separated by database prefix (mysql_, mongo_, redis_) and distinct actions (list, describe, query, execute, find, aggregate, insert, update, delete). Read vs write vs specialized operations are clearly delineated in descriptions, leaving no meaningful ambiguity.
All names follow a consistent snake_case pattern with a database prefix and verb-based naming. Minor verb variations (query/find/command) are conventional for each database and do not break predictability.
18 tools across three databases (MySQL, MongoDB, Redis) is well-scoped; each database has a focused set covering essential read/write operations without redundancy. The count is justified by the multi-database purpose.
Covers core CRUD for MySQL (via execute), MongoDB, and Redis (via allowlisted commands), with safety constraints. Minor gaps include no batch insert for MongoDB, no single-document update/delete, and no explicit Redis key deletion/expiration tools.