AWS S3 Connector MCP Server
Related Servers
Alternatives to AWS S3 Connector MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables interaction with AWS S3 storage through bucket operations (create, delete, list), object management (upload, download, delete, list), and bucket policy configuration using AWS credentials.21 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query S3 data lakes using natural language, with support for CSV, JSON, Parquet and tools for data discovery, analysis, and metadata exploration.1MIT
- AlicenseNot gradedqualityFmaintenanceEnables CRUD operations on NocoDB tables via natural language commands, supporting table manipulation, file upload, and bulk actions.72 npm75MIT
- AlicenseAqualityDmaintenanceEnables interaction with S3-compatible storage services like AWS S3 and Cloudflare R2, supporting bucket management, object listing, reading, uploading, and deletion operations.5199 npmISC
- FlicenseAqualityDmaintenanceEnables users to execute SQL queries, manage workgroups, databases, tables, and named queries in AWS Athena through natural language.15-
- AlicenseNot gradedqualityAmaintenanceProvides MCP tools for AWS S3 and S3-compatible storage, enabling file upload, download, listing, deletion, and temporary remote file staging via natural language.BSD 3-Clause
TDQS
Scored across 17 tools
Each tool targets a distinct operation on S3 Tables or related resources (e.g., bucket creation, namespace management, table CRUD, metadata, maintenance, data import/query, and connection setup). There is no overlap between tool purposes.
All tools follow a clear verb_noun (or verb_noun_noun) pattern, e.g., create_table_bucket, list_namespaces, get_table_metadata_location. No mixing of conventions like camelCase or inconsistent verb forms.
17 tools cover a broad domain of S3 Tables management, data operations, and connectivity. While slightly above the typical 3-15 range, they are well-scoped for the server's stated purpose.
Missing essential CRUD operations like delete (table, namespace, table bucket) and update (except metadata location). No tool to retrieve table schema or detailed table info beyond metadata location. Significant lifecycle gaps exist.