aws-athena-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | No | AWS region to use for Athena queries | AWS CLI default region |
| AWS_PROFILE | No | AWS profile name to use for credentials | default |
| MAX_RETRIES | No | Maximum number of retry attempts for query status checks | 100 |
| OUTPUT_S3_PATH | Yes | S3 path where Athena query results will be stored (e.g., s3://your-bucket/athena-results/) | |
| RETRY_DELAY_MS | No | Delay between retry attempts in milliseconds | 500 |
| QUERY_TIMEOUT_MS | No | Maximum time to wait for query completion in milliseconds | 300000 |
| AWS_ACCESS_KEY_ID | No | AWS access key ID | |
| AWS_SESSION_TOKEN | No | AWS session token | |
| AWS_SECRET_ACCESS_KEY | No | AWS secret access key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_queryA | Execute a SQL query using AWS Athena. Returns full results if query completes before timeout, otherwise returns queryExecutionId. |
| get_resultA | Get results for a completed query. Returns error if query is still running. |
| get_statusC | Get the current status of a query execution |
| run_saved_queryC | Execute a saved (named) Athena query by its query ID. |
| list_saved_queriesA | List all saved (named) Athena queries available in your AWS account. |
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 5 tools
Each tool has a clearly distinct purpose with no overlap: get_result retrieves results, get_status checks status, list_saved_queries lists queries, run_query executes new queries, and run_saved_query executes saved ones. The descriptions make it unambiguous which tool to use for each operation.
All tools follow a consistent verb_noun pattern with snake_case: get_result, get_status, list_saved_queries, run_query, and run_saved_query. This predictable naming makes it easy for agents to understand and select tools.
With 5 tools, this server is well-scoped for AWS Athena operations. Each tool earns its place by covering essential query lifecycle functions: listing, executing (both new and saved), checking status, and retrieving results. This is an appropriate number for the domain.
The tool set provides complete coverage for core Athena workflows: create/run queries (run_query, run_saved_query), monitor (get_status), and retrieve results (get_result), with list_saved_queries for discovery. A minor gap is the lack of tools for managing saved queries (e.g., create, update, delete), but agents can work around this.