everything vs aws-s3-mcp
Side-by-side comparison to help you pick between these two MCP servers.
everything by modelcontextprotocol | aws-s3-mcp by samuraikun | |
|---|---|---|
| Stars | ★ 85,748 | ★ 24 |
| 30d uses | — | — |
| Score | 77 | 42 |
| Official | ✓ | — |
| Categories | Developer ToolsAI / LLM ToolsOther | Cloud StorageDeveloper ToolsAI / LLM Tools |
| Language | TypeScript | TypeScript |
| Last commit | this month | 3 mo ago |
everything · Summary
Official MCP test server exercising all protocol features for client builders.
aws-s3-mcp · Summary
A well-designed MCP server for AWS S3 integration with both HTTP and STDIO transport support.
everything · Use cases
- Testing MCP client implementations against all protocol features
- Learning MCP protocol capabilities through a reference server
- Validating client compatibility with different transport methods
aws-s3-mcp · Use cases
- Enabling LLMs to access and retrieve data from AWS S3 buckets
- Building applications that allow AI assistants to browse and process files stored in S3
- Creating MCP-based workflows that integrate S3 operations into AI agent behavior
everything · Install
NPX (recommended)
{
"mcpServers": {
"everything": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-everything"]
}
}
}On Windows, use cmd /c:
{
"mcpServers": {
"everything": {
"command": "cmd",
"args": ["/c", "npx", "-y", "@modelcontextprotocol/server-everything"]
}
}
}Docker
{
"mcpServers": {
"everything": {
"command": "docker",
"args": ["run", "-i", "--rm", "mcp/everything"]
}
}
}Global install
npm install -g @modelcontextprotocol/server-everything@latest
npx @modelcontextprotocol/server-everythingaws-s3-mcp · Install
Installation
- Install via npm:
npm install -g aws-s3-mcp- Configure AWS credentials (environment variables or .env file)
- Run with HTTP transport:
npx aws-s3-mcpOr with STDIO for Claude Desktop:
npx aws-s3-mcp --stdio- For Claude Desktop integration, add to config:
{
"mcpServers": {
"s3": {
"command": "npx",
"args": ["aws-s3-mcp", "--stdio"],
"env": {
"AWS_REGION": "us-east-1",
"S3_BUCKETS": "bucket1,bucket2,bucket3",
"AWS_ACCESS_KEY_ID": "your-access-key",
"AWS_SECRET_ACCESS_KEY": "your-secret-key"
}
}
}
}