Amazon Athena MCP Server by CData

1. Open FastMCP and click “Install Now”

   • In the FastMCP connection interface use the existing "Install Now" button. You will enter the required ENV values directly into the FastMCP connection form fields described in the steps below.

2. Download and license the CData JDBC Driver for Amazon Athena

   • Download the driver (cdata.jdbc.amazonathena.jar) from CData’s Athena JDBC driver page and place the JAR somewhere on the machine FastMCP will use. The license file (cdata.jdbc.amazonathena.lic) must sit next to the JAR. (cdn.cdata.com)

3. Locate the JDBC driver class name and driver JAR path

   • DriverClass: cdata.jdbc.amazonathena.AmazonAthenaDriver (use this value in the connection).
   • DriverPath: full filesystem path to cdata.jdbc.amazonathena.jar (e.g., /path/to/cdata.jdbc.amazonathena.jar). (cdn.cdata.com)

4. Create an AWS IAM identity for programmatic access (to get AWS credentials)

   • In the AWS Console go to IAM → Users → Create user. Choose “Programmatic access”.
   • Attach appropriate permissions (for testing you can use AmazonAthenaFullAccess + AmazonS3FullAccess or follow least-privilege guidance—see Minimum IAM Permissions in the CData docs). After creation, download the Access key ID and Secret access key CSV and store it securely. (cdn.cdata.com)

5. Create or choose an S3 bucket for Athena query results (S3 staging directory)

   • In the AWS Console → S3, create a bucket (or pick an existing one) and note its S3 URI (e.g., s3://my-athena-query-results/). This will be the S3StagingDirectory value used by the JDBC driver. Also note the AWS region of the bucket/account. (cdn.cdata.com)

6. (Optional) Configure temporary/sts credentials or role chaining if you prefer not to use static keys

   • If you will use role-based or temporary credentials (STS, SSO, or AWS profiles), note the relevant values (AWSRoleARN, AWSSessionToken, AWSCredentialsFile, AWSCredentialsFileProfile, etc.)—these are supported connection options in the CData driver. (cdn.cdata.com)

7. Build the JDBC connection string

   • Use the CData Connection String utility (run: java -jar cdata.jdbc.amazonathena.jar) or construct a JDBC URL manually. Typical properties you will include in the JDBC URL: AWSAccessKey, AWSSecretKey (or AWSSessionToken), S3StagingDirectory, AWSRegion, and any optional properties (Workgroup, AuthScheme, InitiateOAuth if using OAuth flows). Example structure (replace placeholders with your values):
     jdbc:amazonathena:AWSAccessKey=YOUR_AWS_ACCESS_KEY;AWSSecretKey=YOUR_AWS_SECRET;S3StagingDirectory=s3://your-bucket/;AWSRegion=us-east-1;
     (Do not paste real secrets into public places — use the FastMCP secure ENV fields.) (cdn.cdata.com)

8. Create the .prp (property) file for the MCP server (local copy)

   • Create a file (e.g., amazon-athena.prp) that includes:
     • Prefix (e.g., amazonathena)
     • ServerName and ServerVersion
     • DriverPath (full path to the JAR)
     • DriverClass (cdata.jdbc.amazonathena.AmazonAthenaDriver)
     • JdbcUrl (the JDBC URL you built)
     • Tables (optional — leave blank to expose all)
   • Keep this .prp file accessible to FastMCP or the process that will launch the MCP server. (See README for format.) (cdn.cdata.com)

9. Fill the FastMCP “Install Now” ENV fields

   • In the FastMCP connection interface, enter the values into the ENV/key fields (use secure/secret fields for secrets). Example ENV keys to add:
     • DRIVER_PATH — /full/path/to/cdata.jdbc.amazonathena.jar
     • DRIVER_CLASS — cdata.jdbc.amazonathena.AmazonAthenaDriver
     • JDBC_URL — (jdbc:amazonathena:... as built above)
     • AWS_ACCESS_KEY_ID — your AWS Access Key ID (secure field)
     • AWS_SECRET_ACCESS_KEY — your AWS Secret Access Key (secure field)
     • S3_STAGING_DIRECTORY — s3://your-athena-bucket/
     • AWS_REGION — e.g., us-east-1
     • OPTIONAL: AWS_SESSION_TOKEN / AWS_ROLE_ARN / AWSCREDENTIALSFILE / AWSCREDENTIALSPROFILE if using temporary or profile-based credentials
     • OPTIONAL: WORKGROUP — if you use an Athena workgroup
   • Ensure secrets are entered into FastMCP’s secure/secret input types (not a visible/plain field).

10. Install and verify

• Click Install (or the equivalent confirmation in the FastMCP UI).
  - Verify the connection by asking the MCP tools for tables/columns (e.g., call amazon_athena_get_tables or run a simple query). If it fails, confirm DriverPath, JDBC_URL, and AWS credentials, and check the driver license file location. (cdn.cdata.com)

11. Troubleshooting & security reminders

• Keep the license file next to the JAR and never commit secrets to source control.
  - If you need least-privilege IAM guidance or run into permission issues, consult the driver’s “Minimum IAM Permissions” section in the CData docs. (cdn.cdata.com)

If you want, tell me the exact FastMCP ENV field names shown in your Install Now dialog and I’ll map the values above to those field names exactly.