athena-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | Yes | Your AWS region. | |
| AWS_ACCESS_KEY_ID | Yes | Your AWS access key ID. | |
| AWS_SESSION_TOKEN | No | Your AWS session token (optional). | |
| AWS_SECRET_ACCESS_KEY | Yes | Your 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
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 |
|---|---|
| list_work_groupsA | List all Athena work groups Args: max_results: Maximum number of results to return next_token: Token for pagination |
| list_databasesA | List databases in a data catalog Args: catalog_name: Name of the data catalog max_results: Maximum number of results to return next_token: Token for pagination |
| list_tablesA | List tables in a database Args: database_name: Name of the database catalog_name: Name of the data catalog expression: Regular expression to filter table names max_results: Maximum number of results to return next_token: Token for pagination |
| get_table_metadataC | Get metadata for a specific table Args: database_name: Name of the database table_name: Name of the table catalog_name: Name of the data catalog |
| start_query_executionC | Execute a SQL query in Athena Args: query_string: SQL query to execute database: Database to run query in catalog: Catalog to run query in work_group: Work group to use output_location: S3 location for query results |
| get_query_executionC | Get details about a query execution Args: query_execution_id: Query execution ID |
| get_query_resultsB | Get results from a completed query Args: query_execution_id: Query execution ID max_results: Maximum number of results to return next_token: Token for pagination |
| stop_query_executionB | Stop a running query execution Args: query_execution_id: Query execution ID |
| list_query_executionsC | List recent query executions Args: work_group: Work group to filter by max_results: Maximum number of results to return next_token: Token for pagination |
| create_named_queryC | Create a named query Args: name: Name of the query database: Database for the query query_string: SQL query string description: Description of the query work_group: Work group for the query |
| list_named_queriesB | List named queries Args: work_group: Work group to filter by max_results: Maximum number of results to return next_token: Token for pagination |
| get_named_queryC | Get details about a named query Args: named_query_id: Named query ID |
| delete_named_queryC | Delete a named query Args: named_query_id: Named query ID |
| get_work_groupB | Get details about a work group Args: work_group: Work group name |
| list_data_catalogsB | List data catalogs Args: max_results: Maximum number of results to return next_token: Token for pagination |
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 15 tools
Each tool targets a distinct resource and action: work groups, catalogs, databases, tables, query executions, and named queries are clearly separated. Even similar tools like get_query_execution and get_query_results are unambiguous because one returns execution status and the other returns result rows.
All tool names follow a consistent verb_noun pattern using snake_case, such as list_*, get_*, create_*, delete_*, start_*, and stop_*. This makes the API predictable and easy for an agent to navigate.
Fifteen tools is well-scoped for an Athena MCP server covering catalog discovery, query execution, and named query management. Each tool earns its place and the count stays within the ideal range without redundancy.
The core Athena workflow is well covered: discover catalogs/databases/tables, run and manage query executions, and manage named queries. Minor gaps include the absence of update_named_query and limited work group/catalog management beyond listing and getting details.