AWS MCP Proxy Server vs Docker Hub MCP Server
Infrastructure control from inside Claude. The AWS MCP servers surface AWS services and documentation; the Docker server manages containers, images, and compose stacks on the machine you're already on. Local-first workflows lean Docker; cloud-first estates lean AWS — the activity and license data below is where they differ concretely.
GitHub data verified 2026-07-30 — objective fields only, no editorial scoring.
| AWS MCP Proxy Server Interact with AWS services including S3, Lambda, EC2, and more | Docker Hub MCP Server Manage Docker containers, images, and compose configurations | |
|---|---|---|
| GitHub stars | 331 | 160 |
| Forks | 57 | 101 |
| Open issues | 9 | 7 |
| Last commit | 2026-07-29 | 2026-07-29 |
| Maintenance status | Actively maintained | Actively maintained |
| License | Apache-2.0 | Apache-2.0 |
| Language | TypeScript | TypeScript |
| Author | AWS | Docker |
| Official listing | Yes | Yes |
| Community votes | 0 | 0 |
| Copies from directory | 0 | 0 |
GitHub statistics are measured at repository level; servers that live in a shared monorepo show that repository's stats. This comparison is generated from directory data — no sponsored placement, see the curation policy.