Archery MCP
Related Servers
Alternatives to Archery MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for Microsoft SQL Server that enables AI agents to safely explore and query SQL Server databases.623 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables secure read-only queries and performance diagnostics for MySQL, Redis, and MongoDB databases through the Archery gateway, acting as a bridge between MCP clients and databases.1-
- AlicenseNot gradedqualityDmaintenanceA read-only MCP server for exploring on-premises, multi-instance Microsoft SQL Server estates from AI clients, with read-only enforcement and Windows authentication support.Apache 2.0
- AlicenseAqualityCmaintenanceA read-only MCP server that exposes SQL database access to LLMs, supporting multiple database types, compact columnar results, pagination, and file export.612 npmMIT
- AlicenseNot gradedqualityBmaintenanceA security-first, read-only MCP server for AI assistants to safely query MySQL, PostgreSQL, and Redis with layered safety checks.1MIT
- AlicenseNot gradedqualityDmaintenanceRead-only SQL Server MCP server enabling safe database queries, table listing, and schema inspection with built-in security protections.MIT
TDQS
Scored across 10 tools
Most tools target distinct resources/actions, such as health, login, instance listing, querying, and workflow inspection. However, `list_instances` and `list_query_instances` overlap in scope (both list instances, with subtle permission differences), which could cause occasional misselection.
The `archery_` prefix is used consistently, and most listing tools follow a `list_` pattern. Minor deviations exist with `query`, `export_query`, and `workflow_status`/`workflow_detail`, which don't follow a strict verb_noun structure, but the names remain readable and predictable.
Ten tools provide a well-scoped set for interacting with Archery, covering health, authentication, instance discovery, querying, export, and workflow inspection without exceeding a manageable number.
The tool set covers the core read-oriented workflows: discovering instances/databases, running read-only queries, exporting results, and checking workflow status. Minor gaps exist, such as no tool for retrieving table schemas or creating SQL workflows, but these are acceptable for a read-focused MCP server.