LocalStack MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCALSTACK_AUTH_TOKEN | No | Your LocalStack Auth Token to enable Pro services IAM Policy Analyzer, Cloud Pods, and Chaos Injector tools |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| localstack-aws-clientA | Executes an AWS CLI command against the running LocalStack container using the 'awslocal' wrapper. |
| localstack-chaos-injectorA | Injects, manages, and clears chaos faults and network effects in LocalStack to test system resilience. |
| localstack-cloud-podsB | Manages LocalStack Cloud Pods with following actions: save, load, delete, reset |
| localstack-deployerA | Deploys or destroys AWS infrastructure on LocalStack using CDK or Terraform. |
| localstack-iam-policy-analyzerB | Configures LocalStack's IAM enforcement and analyzes logs to automatically generate missing IAM policies. |
| localstack-logs-analysisB | LocalStack log analyzer that helps developers quickly diagnose issues and understand their LocalStack interactions |
| localstack-managementA | Manage LocalStack lifecycle: start, stop, restart, or check status |
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 7 tools
Each tool has a clearly distinct purpose with no overlap: AWS client execution, chaos injection, cloud pods management, infrastructure deployment, IAM policy analysis, log analysis, and lifecycle management. The descriptions clearly differentiate their domains and functions, making misselection unlikely.
All tools follow a consistent 'localstack-' prefix with descriptive hyphenated suffixes (e.g., aws-client, chaos-injector). This uniform pattern makes the tool set predictable and easy to navigate, with no deviations in naming style.
With 7 tools, the server is well-scoped for managing LocalStack, covering key areas like execution, testing, deployment, security, diagnostics, and lifecycle. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides comprehensive coverage for LocalStack management, including core operations, resilience testing, and diagnostics. A minor gap exists in direct resource management (e.g., creating or querying specific AWS services), but agents can work around this using the AWS client tool.