jmd-mcp-sql
Related Servers
Alternatives to jmd-mcp-sql
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables comprehensive SQLite database management through natural language, including database creation, table operations, data CRUD operations, backup/restore functionality, and CSV import/export capabilities.MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with SQLite databases through natural language, supporting SQL queries, CSV imports, and schema exploration.5 npm-
- FlicenseAqualityDmaintenanceAutomatically scans SQLite databases and generates typed CRUD tools for each table, allowing natural language database interaction without exposing raw SQL.12-
- FlicenseNot gradedqualityCmaintenanceEnables natural language interaction with a corporate SQLite database, allowing users to set up tables, add records, and search data through plain English commands.-
- FlicenseNot gradedqualityDmaintenanceEnables natural language database operations and semantic document search through SQLite and vector database integration. Converts plain English instructions into SQL queries and provides RAG capabilities for uploaded documents.-
- AlicenseBqualityDmaintenanceEnables AI agents to interact with local SQLite databases with full CRUD, schema introspection, foreign key relations, generated columns, and multi-format import/export (CSV, JSON, XLSX) through natural language.268 npmMIT
TDQS
Scored across 4 tools
The four tools are broadly distinct: open manages the database connection/inspection, read queries records/schema, write creates/updates records and DDL, and delete removes records/drops objects. A minor overlap exists between open's inspect mode and read's #! Database schema listing, which could cause an agent to pick either for listing tables.
All tool names are single-word lowercase verbs (open, read, write, delete), forming a perfectly consistent naming style. There is no mixing of conventions or verb patterns.
Four tools is a well-scoped count for a SQLite interface, with each tool covering a fundamental operation: connection, read, write, delete. Although each tool is internally rich with sub-commands, the top-level surface is minimal and each tool earns its place.
The surface covers the full database lifecycle: opening/creating a database, reading and querying data/schema, inserting/replacing records and defining DDL objects, and deleting records or dropping DDL objects. No obvious dead ends exist for the stated JMD-document-based SQLite purpose.