LocalStack MCP Server
A Model Context Protocol server that provides tools to manage your LocalStack container and other assorted related tasks, to simplify local cloud development and testing. The LocalStack MCP Server provides simplified integration between Model Context Protocol-compatible apps and your local AWS development environment, enabling secure and direct communication with LocalStack's assortment of various features.
This server eliminates custom scripts and manual LocalStack management with direct access to:
Start, stop, restart, and monitor LocalStack container status with built-in auth.
Deploy CDK and Terraform projects with automatic configuration detection.
Parse logs, catch errors, and auto-generate IAM policies from violations.
Inject chaos faults and network effects into LocalStack to test system resilience.
Manage LocalStack state snapshots via Cloud Pods for development workflows.
Connect AI assistants and dev tools for automated cloud testing workflows.
Tools Reference
This server provides your AI with dedicated tools for managing your LocalStack environment:
Tool Name | Description | Key Features |
Manages LocalStack container operations and settings | - Execute start, stop, restart, and status checks - Integrate LocalStack Pro authentication tokens - Inject custom environment variables - Verify real-time status and perform health monitoring | |
Handles infrastructure deployment to LocalStack environments | - Automatically run CDK and Terraform tooling to deploy infrastructure locally - Enable parameterized deployments with variable support - Process and present deployment results - Requires you to have or installed in your system path | |
Analyzes LocalStack logs for troubleshooting and insights | - Offer multiple analysis options including summaries, errors, requests, and raw data - Filter by specific services and operations - Generate API call metrics and failure breakdowns - Group errors intelligently and identify patterns | |
Handles IAM policy management and violation remediation | - Set IAM enforcement levels including
,
, and
modes - Search logs for permission-related violations - Generate IAM policies automatically from detected access failures - Requires a valid LocalStack Auth Token | |
Injects and manages chaos engineering faults for system resilience testing | - Inject, add, remove, and clear service fault rules - Configure network latency effects - Comprehensive fault targeting by service, region, and operation - Built-in workflow guidance for chaos experiments | |
Manages LocalStack state snapshots for development workflows | - Save current state as Cloud Pods - Load previously saved Cloud Pods instantly - Delete Cloud Pods or reset to a clean state - Requires a valid LocalStack Auth Token | |
Runs AWS CLI commands inside the LocalStack container | - Executes commands via
inside the running container - Sanitizes commands to block shell chaining - Auto-detects LocalStack coverage errors and links to docs |
Installation
Editor | Installation |
Cursor |
|
For other MCP Clients, refer to the . |
Prerequisites
LocalStack CLI and Docker installed in your system path
cdklocalortflocalinstalled in your system path for running infrastructure deployment toolingA valid LocalStack Auth Token to enable Pro services IAM Policy Analyzer, Cloud Pods, and Chaos Injector tools (optional)
Node.js v22.x installed in your system path
Configuration
Add the following to your MCP client's configuration file (e.g., ~/.cursor/mcp.json). This configuration uses npx to run the server, which will automatically download & install the package if not already present:
If you installed from source, change command and args to point to your local build:
Enabling Licensed Features
To activate LocalStack licensed features, you need to add your LocalStack Auth Token to the environment variables. You can get your LocalStack Auth Token by following the official documentation.
Here's how to add your LocalStack Auth Token to the environment variables:
Contributing
Pull requests are welcomed on GitHub! To get started:
Install Git and Node.js
Clone the repository
Install dependencies with
yarnBuild with
yarn build
Built on the XMCP framework, you can add new tools by adding a new file to the src/tools directory and documenting it in the manifest.json file.
License
local-only server
The server can only run on the client's local machine because it depends on local resources.
Tools
A Model Context Protocol (MCP) server for LocalStack that enables management of local AWS development environments, including container lifecycle operations, infrastructure deployments, log analysis with IAM policy generation, chaos injection, and Cloud Pods state management.