Code Gym AWS Emulator MCP
Related Servers
Alternatives to Code Gym AWS Emulator MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides conversational access to LocalStack AWS services (S3, DynamoDB, Lambda, SQS) through natural language, enabling local cloud infrastructure management without real AWS costs.MIT
- AlicenseNot gradedqualityCmaintenanceProvides a comprehensive suite of tools for interacting with AWS services like S3, EC2, and Lambda using natural language commands. It enables AI assistants to inspect, manage, and operate AWS resources directly through the Model Context Protocol using your local credentials.33 npm1Apache 2.0
- AlicenseBqualityDmaintenanceExposes LocalStack-managed AWS services as AI-agent tools, enabling LLMs and AI agents to interact with local AWS infrastructure during development and testing.7341 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage S3-compatible storage through 39 tools covering buckets, objects, versions, policies, CORS, lifecycle, tags, encryption, presigned URLs, and multipart cleanup, either as a shared Streamable HTTP service or a local stdio process. It turns a local file path into a public URL in a single call while keeping storage credentials on the server.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to discover and invoke filesystem, notes, SQLite, and utility operations over MCP, with a local-first sandbox and dashboard for testing and management.MIT
- FlicenseNot gradedqualityCmaintenanceEnables Codex to discover, lease, start, control, and release registered local Android Studio emulators through a 63-tool catalog with readiness checks, screen-state reads, and lease-bound UI automation.-
TDQS
Scored across 27 tools
The S3, SQS, and DynamoDB tools are cleanly separated by service prefix and action, so agents can choose confidently. The only mild overlap is among emulator status/health/identity/doctor and between self_test and order_demo, which all inspect or exercise the emulator in related ways.
Most tools follow predictable lower_snake_case with a service prefix plus verb/noun, such as s3_create_bucket and sqs_send_message. The emulator_* group uses noun-like suffixes (status, doctor, health, identity) rather than verbs, which is a minor but noticeable deviation.
The 27 tools are split across four coherent areas: emulator lifecycle, S3, SQS, and DynamoDB. It is reasonable for an AWS emulator server but sits above the ideal 3–15 range and feels somewhat heavy.
Core CRUD coverage exists for S3 buckets/objects, SQS queues/messages, and DynamoDB tables/items, plus lifecycle and diagnostic support. Minor gaps remain, such as DynamoDB update/query/scan and richer SQS queue/message operations, but main emulator workflows are covered.