LocalStack MCP Server
Let an AI agent manage and interact with LocalStack on your machine.
IMPORTANT
The LocalStack MCP server is currently available as an experimental public preview. For questions, issues or feedback, please utilize the LocalStack Community slack or submit a GitHub Issue
LocalStack emulates the cloud on your local machine so software teams and AI agents can validate security, quality, and reliability faster and more safely than the cloud allows. This Model Context Protocol (MCP) server lets any MCP client (Cursor, Claude, VS Code, and more) start LocalStack, deploy infrastructure, and debug your local cloud in natural language.
Quick start
Set up the server in your MCP client with the interactive wizard:
npx -y @localstack/localstack-mcp-server init
The wizard detects your installed clients, asks how you want to run the server, and writes the configuration for you. You need a LocalStack Auth Token; the wizard reads LOCALSTACK_AUTH_TOKEN from your environment or asks for it. For the full options, prerequisites, and manual setup, see Installation.
What you can ask your agent
Once the server is configured, talk to LocalStack through your agent in natural language:
- "Start LocalStack and deploy the Terraform project in
./infra, then tell me which resources came up." - "My Lambda calls are failing. Read the LocalStack logs, find the permission errors, and generate an IAM policy that fixes them."
- "Inject 500ms of latency into DynamoDB and confirm my retry logic still works."
- "Search the LocalStack docs for how to enable S3 event notifications and summarize the steps."
How it works
The server connects MCP-compatible apps directly to your local LocalStack environment and its emulated AWS services, so your assistant can operate the stack securely without custom scripts or manual setup.
This server eliminates custom scripts and manual LocalStack management. Your agent can:
- Start, stop, restart, and monitor LocalStack for AWS container status with built-in auth.
- Deploy CDK, Terraform, and SAM projects with automatic configuration detection.
- Search LocalStack documentation for guides, API references, and configuration details.
- 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.
- Export, import, inspect, and reset LocalStack state locally with Export & Import State file-based workflows.
- Install, remove, list, and discover LocalStack Extensions from the marketplace.
- Launch and manage Ephemeral Instances for remote LocalStack testing workflows.
- Replicate external AWS resources into LocalStack with AWS Replicator so IaC stacks can resolve shared dependencies locally.
- Inspect LocalStack application flows with App Inspector traces, spans, events, payload metadata, and IAM policy evaluations.
- Start repeatable LocalStack workflows from ready-made MCP prompts, including infrastructure validation and integration test generation.
Tools
This server provides your AI with dedicated tools for managing your LocalStack environment:
NOTE
All tools in this MCP server require LOCALSTACK_AUTH_TOKEN.
| Tool Name | Description | Key Features |
|---|---|---|
localstack-management | Manages LocalStack runtime operations for AWS and Snowflake stacks | - Execute start, stop, restart, and status checks<br/>- Integrate LocalStack authentication tokens<br/>- Inject custom environment variables<br/>- Verify real-time status and perform health monitoring |
localstack-deployer | Handles infrastructure deployment to LocalStack for AWS environments | - Automatically run CDK, Terraform, and SAM tooling to deploy infrastructure locally<br/>- Enable parameterized deployments with variable support<br/>- Process and present deployment results<br/>- Requires you to have cdklocal, tflocal, or samlocal installed in your system path |
localstack-logs-analysis | Analyzes LocalStack for AWS logs for troubleshooting and insights | - Offer multiple analysis options including summaries, errors, requests, and raw data<br/>- Filter by specific services and operations<br/>- Generate API call metrics and failure breakdowns<br/>- Group errors intelligently and identify patterns |
localstack-iam-policy-analyzer | Handles IAM policy management and violation remediation | - Set IAM enforcement levels including enforced, soft, and disabled modes<br/>- Search logs for permission-related violations<br/>- Generate IAM policies automatically from detected access failures<br/>- Requires a valid LocalStack Auth Token |
localstack-chaos-injector | Injects and manages chaos experiment faults for system resilience testing | - Inject, add, remove, and clear service fault rules<br/>- Configure network latency effects<br/>- Comprehensive fault targeting by service, region, and operation<br/>- Built-in workflow guidance for chaos experiments<br/>- Requires a valid LocalStack Auth Token |
localstack-cloud-pods | Manages remote LocalStack Cloud Pods for development workflows | - Save current state as a Cloud Pod<br/>- Load previously saved Cloud Pods instantly<br/>- Delete Cloud Pods from remote cloud-backed storage<br/>- Use this for managed remote state snapshots, not local export/import files<br/>- Requires a valid LocalStack Auth Token |
localstack-state-management | Manages local file-based LocalStack state export/import workflows | - Export LocalStack state to a local file on disk through the LocalStack State REST API<br/>- Import LocalStack state from a local file<br/>- Inspect current LocalStack state as JSON metamodel data<br/>- Reset all state or only selected services<br/>- Supports service-level granularity for export, reset, and inspect<br/>- Use this for local disk workflows; use Cloud Pods for remote cloud-backed snapshots<br/>- Requires a valid LocalStack Auth Token |
localstack-extensions | Installs, uninstalls, lists, and discovers LocalStack Extensions | - Manage installed extensions via CLI actions (list, install, uninstall)<br/>- Browse the LocalStack Extensions marketplace (available)<br/>- Requires a valid LocalStack Auth Token |
localstack-ephemeral-instances | Manages cloud-hosted LocalStack Ephemeral Instances | - Create temporary cloud-hosted LocalStack instances and get an endpoint URL<br/>- List available ephemeral instances, fetch logs, and delete instances<br/>- Supports lifetime, extension preload, Cloud Pod preload, and custom env vars on create<br/>- Requires a valid LocalStack Auth Token and LocalStack CLI |
localstack-aws-client | Runs AWS CLI commands inside the LocalStack for AWS container | - Executes commands via awslocal inside the running container<br/>- Sanitizes commands to block shell chaining<br/>- Auto-detects LocalStack coverage errors and links to docs |
localstack-aws-replicator | Replicates external AWS resources into a running LocalStack instance | - Start single-resource replication jobs with a resource type and identifier or ARN<br/>- Start batch replication jobs, such as SSM parameters under a path prefix<br/>- Poll job status by job ID and list existing jobs<br/>- List resource types supported by the running Replicator extension<br/>- Reads source AWS credentials from the MCP server environment and supports optional target account or region overrides |
localstack-app-inspector | Inspects LocalStack application traces, spans, events, and IAM evaluations | - Enable or disable App Inspector for the running LocalStack instance<br/>- List and inspect traces to understand AWS service-to-service flows<br/>- Drill into spans, events, payload metadata, and IAM policy evaluation events<br/>- Filter by service, region, operation, resource, ARN, status, and time range<br/>- Requires a valid LocalStack Auth Token and the App Inspector feature in the connected LocalStack license |
localstack-docs | Searches LocalStack documentation through CrawlChat | - Queries LocalStack docs through a public CrawlChat collection<br/>- Returns focused snippets with source links only<br/>- Helps answer coverage, configuration, and setup questions without requiring LocalStack runtime |
localstack-snowflake-client | Runs SQL against the LocalStack Snowflake emulator through the snow CLI | - Execute SELECT, DDL (CREATE/DROP), DML (INSERT/UPDATE/DELETE), and SHOW/DESCRIBE statements from a query string or a .sql file<br/>- Check the Snowflake connection before running queries<br/>- Set optional database, schema, warehouse, and role context per query<br/>- Requires the Snowflake CLI (snow) and a valid LocalStack Auth Token |
Prompts
Prompts are user-selected workflow templates exposed by MCP clients as slash commands or quick actions. They frame multi-step LocalStack tasks so the assistant follows the same phases, evidence requirements, and reporting format every time.
| Prompt Name | Description | Arguments |
|---|---|---|
infrastructure-tester | Deploys an IaC project to LocalStack, validates declared resources with live AWS probes and App Inspector evidence, then writes and runs deterministic integration tests. | iac_path (required), iac_type, test_language, test_framework, mode, services_focus, user_focus |
Installation
Set up with the wizard (recommended)
The fastest way to install the MCP server is the interactive setup wizard:
npx -y @localstack/localstack-mcp-server init
The wizard:
- lets you choose how to run the server (
npxon your machine, or the self-contained Docker image), - checks the prerequisites (Node.js, a LocalStack lifecycle CLI, Docker) and tells you how to fix anything missing,
- picks up your
LOCALSTACK_AUTH_TOKENfrom the environment, or asks for it, - lets you pass extra LocalStack config (e.g.
DEBUG=1,PERSISTENCE=1), - detects your installed MCP clients (Cursor, Antigravity, Claude Code, Claude Desktop, VS Code, Codex, OpenCode, Amazon Q CLI) and writes the right configuration for each one you select.
It can also run fully non-interactively, e.g. in dotfiles or scripts:
npx -y @localstack/localstack-mcp-server init --method npx --client cursor,claude-code --yes
To remove the server from your clients again:
npx -y @localstack/localstack-mcp-server remove
Run npx -y @localstack/localstack-mcp-server init --help for all options.
Prerequisites
- A LocalStack lifecycle CLI (
localstackorlstk) and Docker installed in your system path if you want the MCP server to start or restart LocalStack cdklocal,tflocal, orsamlocalinstalled in your system path if you want to deploy CDK, Terraform, or SAM projects- Snowflake CLI (
snow) installed in your system path if you want to use the Snowflake tool - A valid LocalStack Auth Token configured as
LOCALSTACK_AUTH_TOKEN(required for all MCP tools) - Node.js v20 or higher installed in your system path
Run with npx
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 and install the package if needed. LocalStack and any deployment CLIs used by tools run from your host PATH.
{
"mcpServers": {
"localstack": {
"command": "npx",
"args": ["-y", "@localstack/localstack-mcp-server"],
"env": {
"LOCALSTACK_AUTH_TOKEN": "<YOUR_TOKEN>"
}
}
}
}
All LocalStack MCP tools require LOCALSTACK_AUTH_TOKEN to be set. You can get your LocalStack Auth Token by following the official documentation.
Run from source
If you installed from source, change command and args to point to your local build:
{
"mcpServers": {
"localstack": {
"command": "node",
"args": ["/path/to/your/localstack-mcp-server/dist/stdio.js"],
"env": {
"LOCALSTACK_AUTH_TOKEN": "<YOUR_TOKEN>"
}
}
}
}
Run with Docker
The localstack/localstack-mcp-server Docker image bundles the LocalStack CLI, awslocal, Terraform/tflocal, CDK/cdklocal, SAM/samlocal, Snowflake CLI, and Docker CLI. The only required host dependency is Docker. The container uses the mounted Docker socket to run LocalStack as a sibling container on the host.
If you use the deployer tool with local Terraform, CDK, or SAM projects, bind-mount those project paths into the MCP container and pass the in-container path to the tool. The simplest convention is to mount projects at the same absolute path they use on the host.
{
"mcpServers": {
"localstack": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-v", "/var/run/docker.sock:/var/run/docker.sock",
"-v", "/Users/you/.localstack-mcp:/Users/you/.localstack-mcp",
"-e", "XDG_CACHE_HOME=/Users/you/.localstack-mcp",
"--add-host", "host.docker.internal:host-gateway",
"--add-host", "s3.host.docker.internal:host-gateway",
"--add-host", "snowflake.localhost.localstack.cloud:host-gateway",
"-e", "LOCALSTACK_AUTH_TOKEN",
"-e", "LOCALSTACK_HOSTNAME=host.docker.internal",
"-v", "/Users/you/projects:/Users/you/projects",
"localstack/localstack-mcp-server:latest"
],
"env": { "LOCALSTACK_AUTH_TOKEN": "<YOUR_TOKEN>" }
}
}
}
See docs/DOCKER.md for the run command, MCP client config, IaC project mounts, CDK notes, and troubleshooting.
LocalStack configuration
| Variable Name | Description | Default Value |
|---|---|---|
LOCALSTACK_AUTH_TOKEN (required) | The LocalStack Auth Token to use for the MCP server | None |
MAIN_CONTAINER_NAME | The explicit LocalStack container name to use for Docker-based tools. When unset, the server auto-detects standard LocalStack containers such as localstack-main and localstack-aws, then LocalStack Docker images. | Auto-detect |
MCP_ANALYTICS_DISABLED | Disable MCP analytics when set to 1 | 0 |
APP_INSPECTOR | Set to 1 in the LocalStack container environment to enable App Inspector by default across restarts. The MCP tool can also toggle App Inspector at runtime with set-status. | 0 |
AWS_ACCESS_KEY_ID (required for AWS Replicator tool) | Source AWS access key used by AWS Replicator to read external AWS resources | None |
AWS_SECRET_ACCESS_KEY (required for AWS Replicator tool) | Source AWS secret access key used by AWS Replicator to read external AWS resources | None |
AWS_DEFAULT_REGION (required for AWS Replicator tool) | Source AWS region used by AWS Replicator | None |
For AWS Replicator-specific source credentials, you can use the AWS_REPLICATOR_SOURCE_ prefixed variants instead of the unprefixed variants. Do not mix the prefixed and unprefixed source credential groups; when any AWS_REPLICATOR_SOURCE_ variable is set, the Replicator tool reads the source configuration only from that group.
Contributing
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.
Pull requests are welcomed on GitHub! To get started:
- Install Git and Node.js
- Clone the repository
- Install dependencies with
yarn - Build with
yarn build
MCP Server Tester
This repository includes MCP Server Tester for tool validation in direct mode and LLM host mode.
- Run direct MCP tests (deterministic):
yarn test:mcp:direct - Run Gemini-based MCP host evals:
export GOOGLE_GENERATIVE_AI_API_KEY="<your-gemini-key>" export LOCALSTACK_AUTH_TOKEN="<your-localstack-auth-token>" yarn test:mcp:evals - Open the latest MCP Server Tester HTML report:
npx mcp-server-tester open - Run both:
yarn test:mcp
Notes:
- MCP tests target the local STDIO server command
node dist/stdio.jsby default. LOCALSTACK_AUTH_TOKENis required for all MCP tool usage and test suites.- You can override the target command with:
MCP_TEST_COMMANDMCP_TEST_ARGS(space-separated arguments)