Code Gym AWS Emulator MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| emulator_statusB | Inspect official local AWS Emulator status |
| emulator_doctorB | Diagnose local install, CA, credentials, TLS, and STS with safe fixes |
| emulator_startB | Start official AWS Emulator with telemetry disabled |
| emulator_stopA | Stop only an MCP-managed emulator process |
| emulator_healthC | Check local HTTPS emulator health |
| emulator_identityB | Verify isolated STS account 000000000000 |
| s3_create_bucketC | Create emulated S3 bucket |
| s3_list_bucketsA | List emulated S3 buckets |
| s3_list_objectsC | List keys in emulated S3 bucket |
| s3_put_objectC | Put UTF-8 text in emulated S3 |
| s3_get_objectC | Read UTF-8 text from emulated S3 |
| s3_delete_objectC | Delete emulated S3 object |
| s3_delete_bucketB | Delete empty emulated S3 bucket |
| sqs_create_queueC | Create emulated SQS standard queue |
| sqs_list_queuesA | List emulated SQS queue names |
| sqs_send_messageC | Send text message to emulated SQS |
| sqs_receive_messagesC | Receive up to one emulated SQS message |
| sqs_delete_messageC | Delete emulated SQS message by receipt handle |
| sqs_delete_queueC | Delete an emulated SQS queue |
| emulator_self_testA | Run isolated local S3, DynamoDB, and SQS round trips, with cleanup |
| emulator_order_demoB | Run synthetic S3 + DynamoDB + SQS order workflow with a controlled failure, repair, and cleanup |
| dynamodb_list_tablesB | List emulated DynamoDB tables |
| dynamodb_describe_tableC | Describe emulated DynamoDB table |
| dynamodb_create_tableC | Create DynamoDB table with string id key |
| dynamodb_put_itemC | Store id and message strings |
| dynamodb_get_itemC | Read DynamoDB item |
| dynamodb_delete_tableC | Delete emulated DynamoDB table |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.