LocalStack

The LocalStack MCP Server provides a focused interface to manage and interact with your LocalStack for AWS containers right from your development environment. It simplifies starting, stopping, and monitoring LocalStack, runs CDK and Terraform deployments locally, analyzes logs, and enables advanced testing workflows through licensed features when you supply an auth token.

How to use

You connect to the LocalStack MCP Server through an MCP client, then use the dedicated tools to perform common tasks. Start by loading the server configuration in your MCP client, then choose from operations such as starting LocalStack, deploying infrastructure, analyzing logs, and injecting chaos for resilience testing. When you enable licensed features, you provide an authentication token that unlocks additional capabilities.

How to install

Prerequisites you need before installing the MCP server:

• LocalStack CLI and Docker installed in your system path
• cdklocal or tflocal installed in your system path for running infrastructure deployment tooling
• A valid LocalStack Auth Token to enable Pro features (optional)
• Node.js v22.x installed in your system path

Follow these concrete steps to install and run the MCP server from your MCP client configuration. You will use npx to pull the server package the first time, and you can switch to a local build later if you clone the project and build it yourself.

{
  "mcpServers": {
    "localstack_mcp_server": {
      "command": "npx",
      "args": ["-y", "@localstack/localstack-mcp-server"]
    }
  }
}

Alternative local run from source

If you are running from a local source build, use the absolute path to the built entry point and start the server with node.

{
  "mcpServers": {
    "localstack_mcp_server": {
      "command": "node",
      "args": ["/path/to/your/localstack-mcp-server/dist/stdio.js"]
    }
  }
}

Enabling licensed features

To activate LocalStack licensed features, include your LocalStack Auth Token in the environment variables for the MCP server. This enables tools like IAM policy analysis, Cloud Pods, and chaos testing.

{
  "mcpServers": {
    "localstack_mcp_server": {
      "command": "npx",
      "args": ["-y", "@localstack/localstack-mcp-server"],
      "env": {
        "LOCALSTACK_AUTH_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

Available tools

localstack-management

Manages LocalStack for AWS container operations and settings; start/stop/restart/status, auth integration, environment variable injection, and health monitoring.

localstack-deployer

Automates deployment of infrastructure to LocalStack using CDK and Terraform; supports parameterized deployments and requires cdklocal or tflocal in your PATH.

localstack-logs-analysis

Analyzes LocalStack logs for troubleshooting and insights; supports summaries, error grouping, and metrics by service/operation.

localstack-iam-policy-analyzer

Sets IAM enforcement levels, searches logs for permission violations, and auto-generates IAM policies from detected access failures; requires a valid LocalStack Auth Token.

localstack-chaos-injector

Injects and manages chaos experiments to test system resilience; supports fault rules, latency, and guided workflows; requires a valid LocalStack Auth Token.

localstack-cloud-pods

Manages LocalStack state snapshots for development; save, load, delete, and reset Cloud Pods with a valid token.

localstack-aws-client

Runs AWS CLI commands inside the LocalStack container via awslocal; sanitizes commands and detects LocalStack coverage errors with links to docs.