archery-mcp
Related Servers
Alternatives to archery-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables read-only SQL database access for AI assistants, allowing schema exploration and safe query execution without risk of data modification.-
- AlicenseNot gradedqualityCmaintenanceProvides AI assistants with read-only access to inspect database schemas, preview data, and run safe queries across PostgreSQL, MySQL, MongoDB, and SQL Server. It enables AI tools to understand database structures and relationships automatically to generate more accurate code.15 npm7MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to query SQL databases safely with read-only access, allowing schema discovery and SELECT queries while blocking writes and DDL operations.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to securely discover database schemas and execute read-only SQL queries through guardrailed tools that block mutations and clamp result sizes.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to query a Postgres data warehouse through a governed, read-only SQL interface with policy enforcement, row limits, schema-level PII isolation, and a full audit trail.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to safely inspect Oracle Database schemas, objects, and PL/SQL source with a strict read-only guard, without ever modifying data.11 npmMIT
TDQS
Scored across 5 tools
Each tool targets a distinct resource/action: list_tables (enumerate), describe_table (schema detail), query (execute SQL), query_history (own past queries), and sql_check (validate deployment SQL). The only mild adjacency is query vs sql_check, but their descriptions clearly separate execution from compliance validation.
Names follow a mostly consistent snake_case pattern (list_tables, describe_table, query_history, sql_check), with the lone bare 'query' being a minor deviation from the verb_noun style. Still readable and predictable throughout.
Five tools is well-scoped for a database access server: just enough to discover schema, run queries, review history, and validate deploy SQL without redundancy. No filler tools.
Covers the core discovery-query-validate lifecycle (list, describe, query, history, sql_check). Some gaps remain, such as explicit multi-database/target selection, explain/plan inspection, or write/deploy execution, but these are largely outside a read-oriented Archery query scope.