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
- 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.638 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.33 npmMIT
- 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.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query MySQL, ClickHouse, Trino, and S3-compatible object stores through the same local daemon used by VSCode, including running SQL from files and browsing buckets.1MIT
- AlicenseAqualityAmaintenanceRead-only-by-default MySQL/MariaDB, PostgreSQL and SQLite access for AI agents: explore schemas and foreign keys, search, sample, query and EXPLAIN with token-efficient TOON output. Writes only when enabled, always previewed and atomic.1196 PyPIApache 2.0
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.