mcpserve-py
Related Servers
Alternatives to mcpserve-py
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides AI agents read-only analytical access to a SQLite database over stdio, with tools for listing tables, describing schemas, and running paginated SQL queries.-
- FlicenseNot gradedqualityCmaintenanceProvides two MCP tools for querying a synthetic marketing SQLite database and running agent evaluation cases, with read-only SQL guarding and deterministic planning. The server communicates over stdio and supports initialization handshake and tool listing.-
- AlicenseNot gradedqualityDmaintenanceImplements a Model Context Protocol server that enables natural language interactions with SQLite databases, providing tools to list tables, retrieve schemas, count rows, and execute read-only SQL queries.MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server implementation that enables AI assistants to execute SQL queries and interact with SQLite databases through a structured interface.7MIT
- AlicenseNot gradedqualityCmaintenanceRead-only MCP server for SQLite databases, enabling AI assistants to safely query and inspect database schemas without write access.MIT
- FlicenseNot gradedqualityCmaintenanceExposes any SQLite database as read-only MCP tools for AI assistants, enabling listing tables, describing schemas, and running SELECT queries with filtering, ordering, and pagination.-
TDQS
Scored across 8 tools
Most tools target clearly distinct resources and actions, so an agent can pick correctly with little hesitation. The only mild overlap is between list_documents (tag filter) and search_documents (content/title query), which descriptions do disentangle.
Every tool follows a clean verb_noun snake_case pattern: query_database, list_tables, describe_table, create_document, read_document, list_documents, search_documents, get_datetime. No deviations or mixed conventions.
Eight tools is well-scoped for a lightweight multi-purpose server covering database introspection, document management, and a datetime utility. Each tool earns its place with no redundancy.
Document handling lacks update and delete operations, and the database surface is read-only with no insert/update/delete, so lifecycle coverage is partial. The lone get_datetime tool also sits outside either domain, leaving a somewhat heterogeneous surface.