Archery MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARCHERY_URL | Yes | Archery root URL | |
| ARCHERY_TIMEOUT | No | HTTP timeout in seconds, default 30 | 30 |
| ARCHERY_PASSWORD | Yes | Service account password | |
| ARCHERY_USERNAME | Yes | Service account username | |
| ARCHERY_EXPORT_DIR | No | CSV export directory, default 'exports' for Python/EXE, '/exports' in Docker | exports |
| ARCHERY_VERIFY_TLS | No | Whether to verify TLS certificate, default true | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| archery_healthA | 检查 Archery 是否可访问并返回版本；不执行登录。 |
| archery_login_statusA | 使用配置的用户名和密码登录，确认账号可用于 MCP。 |
| archery_list_instancesA | 分页查询当前 Archery 账号有权查看的数据库实例。 |
| archery_list_query_instancesA | 查询当前账号所在资源组中允许只读查询的实例。 |
| archery_list_databasesB | 查询指定可读实例中的数据库；实例归属由 Archery 校验。 |
| archery_queryA | 执行单条受限只读查询；最多返回 5000 行。 |
| archery_export_queryA | 将只读查询分批导出为 CSV；默认每页 5000 行，不限制总行数。 |
| archery_list_workflowsC | 分页查询当前账号有权查看的 SQL 工单。 |
| archery_workflow_statusB | 查询一个有权查看的 SQL 工单当前状态。 |
| archery_workflow_detailB | 查询一个有权查看的 SQL 工单审核或执行明细。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.