Ext Ops Panel
Open dashboard

AWS S3 Tables

Manage S3 Tables for analytics.

MCP server · by awslabs

About

AWS S3 Tables is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). The last change we recorded was on 2026-10-12. As of our marketplace pass on 2026-10-12.

What it asks for

  • Runs on your machine
  • Secrets: 2
  • Settings: 5
  • Tools: 16

Tools it declares: 16. As declared on: Docker MCP Catalog.

  • append_rows_to_table
  • create_namespace
  • create_table
  • create_table_bucket
  • get_bucket_metadata_config
  • get_maintenance_job_status
  • get_table_maintenance_config
  • get_table_metadata_location
  • import_csv_to_table
  • import_parquet_to_table
  • list_namespaces
  • list_table_buckets
Show the remaining 4
  • list_tables
  • query_database
  • rename_table
  • update_table_metadata_location

Requires: AWS_SECRET_ACCESS_KEY (secret), AWS_SESSION_TOKEN (secret)

What it declares, asks for and runs, in full

Only install plugins from developers you trust. We list what marketplaces publish and do not test plugins.

Works with

  • Claude Code
  • Codex
  • Cursor
  • VS Code
  • Copilot CLI

From the marketplaces that list it and the MCP transport it declares, as each client documents them. We do not test plugins.

Connect

Commands and configs built only from what its marketplaces declare. We do not run them for you and do not test plugins.

As a local MCP server: Docker image

Built from what Docker MCP Catalog declares.

Claude CodeTerminal
claude mcp add --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --env "AWS_SESSION_TOKEN=<YOUR_AWS_SESSION_TOKEN>" --transport stdio awslabs-s3-tables -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN mcp/s3-tables-mcp-server
Codex~/.codex/config.toml
[mcp_servers.awslabs-s3-tables]
command = "docker"
args = ["run", "-i", "--rm", "-e", "AWS_SECRET_ACCESS_KEY", "-e", "AWS_SESSION_TOKEN", "mcp/s3-tables-mcp-server"]

[mcp_servers.awslabs-s3-tables.env]
AWS_SECRET_ACCESS_KEY = "<YOUR_AWS_SECRET_ACCESS_KEY>"
AWS_SESSION_TOKEN = "<YOUR_AWS_SESSION_TOKEN>"
Cursor~/.cursor/mcp.json
{
  "mcpServers": {
    "awslabs-s3-tables": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "AWS_SECRET_ACCESS_KEY",
        "-e",
        "AWS_SESSION_TOKEN",
        "mcp/s3-tables-mcp-server"
      ],
      "env": {
        "AWS_SECRET_ACCESS_KEY": "<YOUR_AWS_SECRET_ACCESS_KEY>",
        "AWS_SESSION_TOKEN": "<YOUR_AWS_SESSION_TOKEN>"
      }
    }
  }
}
DockerTerminal
docker run -i --rm -e "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" -e "AWS_SESSION_TOKEN=<YOUR_AWS_SESSION_TOKEN>" mcp/s3-tables-mcp-server

Replace the values in angle brackets with your own. We show the names of the settings, never values.

Optional settings it also lists: AWS_ACCESS_KEY_ID, AWS_PROFILE, AWS_REGION.

We do not store launch arguments. If the server needs any, its own documentation names them.

Where it is published

MarketplaceStatusVersionFiguresVerifiedFirst seen
Docker MCP Catalog (Open on Docker Hub) Listed sha256:6a2cb111afe4 Forks (GitHub): 1 805
Pulls (Docker Hub): 14 048
Stars (Docker Hub): 0
Stars (GitHub): 9 767
Not marked

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

What changed

Nothing has moved on this plugin since we started watching it.

Similar plugins

Its marketplaces publish too short a description to compare this plugin with others by meaning.

Is this your plugin?

Add it to your projects and prove you maintain it with a file in its repository, a file on your domain or a DNS record. You get alerts when a marketplace lists it, drops it, changes its verified mark or what it asks for, and its remote endpoint goes on monitoring as a web service.

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built