get_result
Get results for a completed query. Returns error if query is still running.
LABSCO SUMMARY
A slow query stops being a dead end: you get an ID instead of a timeout.
The timeout is a parameter rather than a wall — run_query hands back rows when it can and a queryExecutionId when it cannot, and get_status and get_result pick it up from there, so an agent can start something expensive and come back to it. maxRows caps what lands in the conversation. The set is read-side: nothing here creates a table or saves a query, and results still land in the S3 path you configured.
What it is
A server over AWS Athena with 5 tools: run a query, poll it, read its result, and reach saved queries by ID.
What you get
- run_query against a named database with a timeoutMs and a maxRows cap, returning full results when the query finishes in time and a queryExecutionId when it does not
- get_status and get_result against that ID, with get_result returning an error while the query is still running rather than a partial answer
- list_saved_queries for the named queries already in the account, and run_saved_query by namedQueryId with an optional databaseOverride
Requirements
OUTPUT_S3_PATH for the S3 location Athena writes results to, and an AWS account with an Athena database the caller can query. MIT licensed.
Setup effort
One command — npx -y @lishenxydlgzs/aws-athena-mcp
USE CASES
01
Getting an answer out of a table that lives in S3
Run the SQL with a row cap so the reply stays readable, check the status when it does not come back inside the timeout, and collect the rows once it has finished.
02
Re-running the analysis someone saved last quarter
List the named queries in the account, run the one you want by its ID, and point it at a different database when the same SQL has to answer for another environment.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_status
Get the current status of a query execution
list_saved_queries
List all saved (named) Athena queries available in your AWS account.
run_query
Execute a SQL query using AWS Athena. Returns full results if query completes before timeout, otherwise returns queryExecutionId.
run_saved_query
Execute a saved (named) Athena query by its query ID.
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected. run_query returns rows only if the query finishes within QUERY_TIMEOUT_MS (five minutes by default); otherwise collect results with get_status and get_result. Results cap at 10,000 rows per call.
Requires
- npx on PATH
- Node.js >= 16
Optional
- AWS_ACCESS_KEY_ID in your environment
- AWS_SECRET_ACCESS_KEY in your environment
- AWS_SESSION_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @lishenxydlgzs/aws-athena-mcpMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"athena": {
"command": "npx",
"args": [
"-y",
"@lishenxydlgzs/aws-athena-mcp"
],
"env": {
"OUTPUT_S3_PATH": "s3://<YOUR_BUCKET>/athena-results/",
"AWS_REGION": "us-east-1",
"AWS_PROFILE": "default",
"AWS_ACCESS_KEY_ID": "",
"AWS_SECRET_ACCESS_KEY": "",
"AWS_SESSION_TOKEN": "",
"ATHENA_WORKGROUP": "default_workgroup",
"QUERY_TIMEOUT_MS": "300000",
"MAX_RETRIES": "100",
"RETRY_DELAY_MS": "500"
}
}
}
}
