AWS Athena MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | No | AWS region for Athena | us-east-1 |
| AWS_PROFILE | No | AWS CLI profile to use | default |
| MAX_RETRIES | No | Maximum number of retry attempts | 100 |
| OUTPUT_S3_PATH | Yes | S3 path for Athena query results (e.g., s3://your-bucket/athena-results/) | |
| RETRY_DELAY_MS | No | Delay between retries in milliseconds | 500 |
| ATHENA_WORKGROUP | No | Athena WorkGroup to use | default_workgroup |
| QUERY_TIMEOUT_MS | No | Query timeout 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 distinct purpose: get_result retrieves query results, get_status checks query status, list_saved_queries lists saved queries, run_query executes a new SQL query, and run_saved_query executes a saved query. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern (e.g., get_result, get_status, list_saved_queries, run_query, run_saved_query). The naming is uniform and predictable across all tools.
With 5 tools, the server is well-scoped for AWS Athena operations. Each tool serves a clear purpose in the query lifecycle, from execution to result retrieval, without being overly complex or sparse.
The tool set covers the full CRUD/lifecycle for Athena queries: creating/executing queries (run_query, run_saved_query), reading results and status (get_result, get_status), and listing saved queries (list_saved_queries). There are no obvious gaps for the domain.