AthenaMCPServer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | No | AWS region where Athena is located | us-east-1 |
| AWS_PROFILE | No | AWS Profile to use for authentication | |
| ATHENA_CATALOG | No | Default catalog/data source to query | AwsDataCatalog |
| ATHENA_DATABASE | No | Default database to query | default |
| ATHENA_WORKGROUP | No | Athena workgroup to use | primary |
| AWS_ACCESS_KEY_ID | No | AWS access key ID for authentication | |
| AWS_SECRET_ACCESS_KEY | No | AWS secret access key for authentication | |
| ATHENA_OUTPUT_LOCATION | No | S3 location for query results | s3://aws-athena-query-results/ |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_athenaB | Execute SQL queries against Amazon Athena and retrieve results |
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 1 tool
With only one tool, there is no possibility of overlap or confusion. The tool's purpose is clearly defined as executing SQL queries and retrieving results.
The name 'query_athena' follows a clear verb_noun pattern with snake_case. While there is only one tool, the name is consistent with common MCP naming conventions and unambiguous.
A single tool feels thin for a server dedicated to Athena, though the narrow purpose of querying makes it borderline acceptable. It falls short of the typical well-scoped 3-15 tool range.
The tool covers the core workflow of executing queries and retrieving results, but lacks explicit operations like query cancellation or schema listing. These can potentially be handled via SQL, representing minor gaps rather than fatal omissions.