AWS Athena MCP Server
Related Servers
Alternatives to AWS Athena MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables users to execute SQL queries, manage workgroups, databases, tables, and named queries in AWS Athena through natural language.15-
- AlicenseNot gradedqualityDmaintenanceEnables execution of SQL queries against AWS Athena databases with schema discovery, query status management, and result retrieval through a standardized Model Context Protocol interface.60 PyPI24MIT
- FlicenseBqualityCmaintenanceEnables AI assistants to discover, explore, and query Formula 1 data stored in AWS, using Athena and Glue for schema inspection, sample data, and custom analytical queries.4-
- AlicenseNot gradedqualityCmaintenanceEnables local MCP-compatible clients, such as Claude Desktop, to query an AWS Athena database with read-only tools for listing tables, describing schemas, running SELECT queries, sampling rows, and getting row counts.ISC
- FlicenseBqualityDmaintenanceEnables AI agents to interact with Amazon Redshift databases using natural language to execute queries, list tables, describe schemas, and retrieve sample data.5-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to query AWS cost and usage data, audit for cloud waste such as idle resources, and monitor budgets using natural language while keeping AWS credentials on the local machine.-
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.