LocalStack MCP Server

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

A Model Context Protocol (MCP) server that provides tools to manage and interact with your LocalStack for AWS container for simplified local cloud development and testing. The LocalStack MCP Server provides simplified integration between MCP-compatible apps and your local LocalStack for AWS development environment, enabling secure and direct communication with LocalStack's emulated services and additional developer experience features.

This server eliminates custom scripts and manual LocalStack management with direct access to:

• Start, stop, restart, and monitor LocalStack for AWS container status with built-in auth.
• Deploy CDK and Terraform 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. (requires active license)
• Inject chaos faults and network effects into LocalStack to test system resilience. (requires active license)
• Manage LocalStack state snapshots via Cloud Pods for development workflows. (requires active license)
• Install, remove, list, and discover LocalStack Extensions from the marketplace. (requires active license)
• 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
localstack-management	Manages LocalStack for AWS container operations and settings	- Execute start, stop, restart, and status checks

• Integrate LocalStack authentication tokens
• Inject custom environment variables
• Verify real-time status and perform health monitoring | | localstack-deployer | Handles infrastructure deployment to LocalStack for AWS 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 cdklocal or tflocal 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
• Filter by specific services and operations
• Generate API call metrics and failure breakdowns
• 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
• Search logs for permission-related violations
• Generate IAM policies automatically from detected access failures
• 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
• Configure network latency effects
• Comprehensive fault targeting by service, region, and operation
• Built-in workflow guidance for chaos experiments
• Requires a valid LocalStack Auth Token | | localstack-cloud-pods | 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 | | localstack-extensions | Installs, uninstalls, lists, and discovers LocalStack Extensions | - Manage installed extensions via CLI actions (list, install, uninstall)
• Browse the LocalStack Extensions marketplace (available)
• Requires a valid LocalStack Auth Token support | | localstack-aws-client | Runs AWS CLI commands inside the LocalStack for AWS container | - Executes commands via awslocal inside the running container
• Sanitizes commands to block shell chaining
• Auto-detects LocalStack coverage errors and links to docs | | localstack-docs | Searches LocalStack documentation through CrawlChat | - Queries LocalStack docs through a public CrawlChat collection
• Returns focused snippets with source links only
• Helps answer coverage, configuration, and setup questions without requiring LocalStack runtime |

Installation

Editor	Installation
Cursor
For other MCP Clients, refer to the configuration guide.

Prerequisites

• 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 services, IAM Policy Analyzer, Cloud Pods, Chaos Injector, and Extensions 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:

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

If you installed from source, change command and args to point to your local build:

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

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:

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

Contributing

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

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

Apache License 2.0