MCP-MongoDB-MySQL-Server
Related Servers
Alternatives to MCP-MongoDB-MySQL-Server
- AlicenseBqualityFmaintenanceThis server enables AI models to interact with MySQL databases through a standardized interface.5156 npm168MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server that provides read-only access to MongoDB databases, enabling AI assistants to directly query and analyze MongoDB data while maintaining data safety.1424 npm9MIT
Related Servers
- FlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI models to interact with MySQL databases through a standardized interface, providing tools for querying, executing commands, and managing database schemas.7-
- AlicenseNot gradedqualityDmaintenanceA comprehensive Model Context Protocol server that enables AI assistants to interact with MySQL databases through secure, role-based database operations.4MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI models to interact with MySQL databases through natural language, supporting SQL queries, table creation, and schema exploration.3-
- AlicenseBqualityDmaintenanceA server based on Model Context Protocol that enables AI models to interact with MySQL databases through a standardized interface, supporting features like query execution, table listing, and automated connection management.417 npm10MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI models to interact with MySQL databases, providing tools for querying, executing statements, listing tables, and describing table structures.5156 npmMIT
- FlicenseNot gradedqualityDmaintenanceA secure MySQL Model Context Protocol server that enables AI agents to interact with MySQL databases through standardized operations. Features comprehensive security with SQL injection prevention, connection pooling, and configurable tool access for database operations.1-
TDQS
Scored across 14 tools
The tools are clearly separated between MySQL and MongoDB operations, but within each database type there is some overlap. For example, 'execute' handles INSERT/UPDATE/DELETE for MySQL while 'query' handles SELECT, but these could potentially be confused with the more specific MongoDB equivalents like 'mongodb_insert' and 'mongodb_find'. The descriptions help clarify, but the boundaries aren't perfectly distinct.
The naming is inconsistent across the set. MySQL tools use simple verb_noun patterns (e.g., 'add_column', 'create_table'), while MongoDB tools use a 'mongodb_' prefix followed by verb_noun (e.g., 'mongodb_create_collection', 'mongodb_find'). This mixing of conventions makes the set less predictable and harder to navigate at a glance.
With 14 tools, the count is reasonable for a server covering two database systems (MySQL and MongoDB). It provides core operations for both, though it might be slightly heavy if considered as a single domain. Each tool appears to serve a distinct function, so the count feels appropriate for the scope.
For MySQL, the tools cover key operations like table management (create, describe, list), column addition, and query execution (SELECT, INSERT/UPDATE/DELETE). For MongoDB, they cover collection management (create, list) and CRUD operations (insert, find, update, delete). Minor gaps include missing operations like dropping tables/collections or more advanced queries, but core workflows are well-covered.