mcp-knowledgebase
Related Servers
Alternatives to mcp-knowledgebase
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to connect to MySQL databases, execute read-only queries, list tables, and describe table schemas via MCP.1-
- AlicenseAqualityDmaintenanceEnables AI agents to query and manage MySQL databases through a structured MCP interface, supporting SQL execution, table inspection, and database operations.95 npmMIT
- AlicenseAqualityBmaintenanceProvides AI agents a secure MCP interface to a single MySQL or MariaDB database, enabling schema inspection, read-only queries, query planning, and guarded write operations with strict safety controls.619 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides read-only access to MySQL databases, enabling schema exploration, table inspection, and safe SELECT query execution via MCP.1-
- AlicenseAqualityCmaintenanceEnables AI assistants to inspect and query a MySQL database through safe, structured tools, including schema discovery and read-only queries.9122 npmMIT
- AlicenseAqualityDmaintenanceSafe MySQL database exploration for AI agents via MCP, enabling read-only queries and schema inspection with three-layer write protection.9MIT
TDQS
Scored across 6 tools
Tools mostly target distinct concerns: schema overview, keys, single-table details, table listing, search, and raw query. However, get_schema and describe_table overlap in providing column/key info, which could confuse an agent choosing between them. Overall boundaries are clear enough with careful reading.
Four tools use the get_ prefix (get_schema, get_keys, get_tables), but describe_table and search_tables use different verbs, and raw_query breaks the pattern entirely. The mix of get_, describe_, search_, and raw_ is readable but not consistent. A unified verb_noun convention would improve predictability.
Six tools is a well-scoped count for a database metadata and query server. Each tool covers a distinct aspect of exploration (schema, keys, tables, search, single-table details, raw queries), with no redundant tools. This is within the ideal range.
The toolset covers the main workflows: understanding schema, relationships, discovering tables, and running read-only queries. Minor gaps exist around indexes, views, or row sampling, but these are not critical for a knowledge base. The core surface is complete for navigation and querying.