pgroonga-mcp
Related Servers
Alternatives to pgroonga-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides read-only access to PostgreSQL databases, enabling users to inspect database schemas and execute read-only queries through a Model Context Protocol server.4-
- AlicenseNot gradedqualityAmaintenanceRead-only PostgreSQL ops/DBA server for the Model Context Protocol, providing diagnostics like slow queries, index health, lock waits, replication lag, and configuration tuning advice.MIT
- AlicenseNot gradedqualityCmaintenanceEnables running SQL queries, DML, DDL, transactions, and schema introspection against a PostgreSQL database through the Model Context Protocol.52 npmISC
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides AI assistants with secure, read-only access to PostgreSQL databases while offering comprehensive tools for schema exploration, query validation, and performance optimization.MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server providing LLMs read-only access to PostgreSQL databases for inspecting schemas and executing queries.64,378 npm27MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server providing read-only access to PostgreSQL databases, enabling LLMs to inspect database schemas and execute read-only SQL queries.64,378 npmMIT
TDQS
Scored across 9 tools
Each tool targets a distinct operation: server info, index listing, search, explain, normalization profiles, text normalization, variant lookup, normalization validation, and health. No two tools appear to do the same thing, and the descriptions make boundaries clear.
All tools share the pgroonga_ prefix and mostly follow a verb_noun pattern (list_indexes, normalize_text, validate_normalization_profile). A few like 'search' and 'health' are simple nouns/verbs, but the overall convention is consistent and predictable.
Nine tools is well-scoped for a domain-specific MCP focused on PGroonga search and normalization. Each tool serves a clear purpose without redundancy or bloat.
The tool surface covers the full workflow: discovering capabilities and indexes, executing and explaining searches, examining normalization, normalizing text, and validating profiles. It lacks explicit search-history or index-creation tools, but for a read-oriented MCP this is complete.