mcp-forge
Related Servers
Alternatives to mcp-forge
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA custom MCP server that gives Claude Desktop direct access to a SQLite database, enabling natural language questions to be answered through real SQL execution.-
- FlicenseNot gradedqualityCmaintenanceA secure, read-only MCP server that empowers Claude Desktop and AI agents to safely query and inspect local SQLite databases.-
- AlicenseAqualityDmaintenanceA zero-config MCP server that enables AI to access, analyze, and manage local SQLite databases with secure read-only querying and automatic schema discovery.829 PyPIMIT
- FlicenseAqualityDmaintenanceA unified MCP server that lets Claude query any SQLite database and build live Streamlit dashboards — all from a single conversation.101-
- AlicenseAqualityDmaintenanceMCP server for Claude that connects to MySQL, MariaDB, and SQLite databases. Query your databases using natural language.3MIT
- AlicenseAqualityCmaintenanceZero-config SQL database MCP server with a browser GUI that connects Claude to MySQL, MariaDB, SQLite, and MSSQL databases.630 npm1MIT
TDQS
Scored across 3 tools
Each tool targets a clearly distinct layer: enumerating tables, inspecting one table's schema, and running row-returning queries. An agent can trivially pick the right one from names alone. No overlap between describe_table (metadata) and execute_query (data).
All three follow the verb_noun snake_case pattern (list_tables, describe_table, execute_query), which is highly predictable. The only minor inconsistency is singular vs. plural nouns (tables vs. table), though that actually reflects list-vs-single semantics.
Three tools is on the thin edge for a database server; a listing, a schema descriptor, and one query executor cover the basics but leave little room for inspection workflows. It's borderline rather than wrong-sized, since the surface is deliberately minimal.
Read-only exploration is covered, but execute_query is explicitly limited to SELECT, so there is no way to create tables, insert, update, or delete — an obvious gap for a database tool. Agents hitting a need to mutate data or run DDL will dead-end, though exploration tasks are fully served.