Log inSubmit server
Localstack MCP Server logo

Localstack MCP Server

by localstack

Manage LocalStack runtime, deployments, logs, IAM violations, chaos tests, and state workflows through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Localstack MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "localstack-localstack-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@localstack/localstack-mcp-server"
      ],
      "env": {
        "LOCALSTACK_AUTH_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 14 tools correctly (19d ago).

Overview

The localstack/localstack-mcp-server MCP server connects MCP-compatible clients to a local LocalStack environment for managing emulated AWS services. It provides tools for starting and monitoring LocalStack, deploying CDK, Terraform, and SAM projects, analyzing logs, generating IAM policies, and injecting faults. Additional workflows cover state management, extensions, ephemeral instances, AWS resource replication, App Inspector data, and documentation search. Reach for it when an agent needs to operate or troubleshoot LocalStack through natural-language requests instead of custom scripts.

Use cases

  • Start and monitor a local LocalStack environment
  • Deploy CDK, Terraform, or SAM infrastructure locally
  • Analyze LocalStack logs and generate IAM policies
  • Inject latency and service faults for resilience tests
  • Save, restore, and inspect LocalStack state

Key features

  • LocalStack lifecycle and health management
  • CDK, Terraform, and SAM deployment support
  • Log analysis and IAM policy generation
  • Chaos fault and latency injection
  • Cloud Pods and file-based state workflows
  • Extensions, replication, and App Inspector workflows

Tools14

What Localstack MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~4.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

19/19 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @localstack/localstack-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars29Stargazers on the source repository.
npm downloads885Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed14Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Localstack MCP Server works

What localstack/localstack-mcp-server MCP server does

The localstack/localstack-mcp-server MCP server lets an MCP client operate a LocalStack environment running on the developer’s machine. LocalStack emulates cloud services locally, while this server exposes agent-facing operations for runtime management, infrastructure deployment, debugging, resilience testing, and state workflows.

Its supported workflows include starting, stopping, restarting, and checking LocalStack status. Agents can deploy local AWS infrastructure from CDK, Terraform, or SAM projects, inspect deployment results, and pass deployment variables. The server can also search LocalStack documentation for guides, API references, and configuration information.

For troubleshooting, the server analyzes logs by producing summaries, error reports, request data, raw output, service or operation filters, API-call metrics, and grouped failure patterns. Its IAM analysis can find permission violations in logs and generate policies based on detected access failures. Chaos testing features can add, remove, or clear service fault rules and apply network latency to selected services, regions, or operations.

How it works

The server connects an MCP-compatible application to the local LocalStack runtime and its emulated AWS services. The agent sends requests through dedicated MCP tools rather than invoking the server’s functions through a custom script. Every tool requires a LocalStack Auth Token, which is also used for authentication-related operations.

AWS Replicator can copy external AWS resources into LocalStack so local infrastructure can resolve shared dependencies. App Inspector workflows expose application-flow traces, spans, events, payload metadata, and IAM policy evaluations.

Setup and configuration

The localstack/localstack-mcp-server MCP server can be configured with the interactive command:

Terminal
npx -y @localstack/localstack-mcp-server init

The setup wizard detects installed MCP clients, asks how the server should run, and writes the client configuration. It reads LOCALSTACK_AUTH_TOKEN from the environment or prompts for the token. A valid token is required by all tools.

Infrastructure deployment also depends on the relevant LocalStack command-line wrapper being installed and available on the system path. CDK deployments require cdklocal, Terraform deployments require tflocal, and SAM deployments require samlocal.

Tools and capabilities

The documented tool groups include:

  • localstack-management for runtime operations, status checks, authentication tokens, custom environment variables, and health monitoring. It supports AWS and Snowflake stacks.
  • localstack-deployer for CDK, Terraform, and SAM deployments with parameters and deployment-result processing.
  • localstack-logs-analysis for filtered log analysis, summaries, errors, requests, raw data, metrics, and failure grouping.
  • localstack-iam-policy-analyzer for IAM enforcement modes, permission-violation searches, and policy generation.
  • localstack-chaos-injector for service fault rules and network-latency experiments.
  • State, extension, ephemeral-instance, replication, App Inspector, and ready-made prompt workflows described in the project documentation.

Limitations and notes

The localstack/localstack-mcp-server MCP server is identified as an experimental public preview. All tools require LOCALSTACK_AUTH_TOKEN, so an installation without that credential cannot use the documented operations. Deployment support is limited to the toolchains and local wrappers named by the project. The README names Cursor, Claude, and VS Code as compatible MCP clients, but does not document client-specific feature differences.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Localstack MCP Server

localstack/localstack-mcp-server is an MCP server that connects MCP-compatible clients to LocalStack on a developer’s machine. Its main tools manage the LocalStack runtime, deploy CDK, Terraform, and SAM infrastructure, analyze logs, find IAM violations, generate policies, and inject service faults or network latency for testing.

Run `npx -y @localstack/localstack-mcp-server init`. The interactive wizard detects installed MCP clients, asks how to run the server, and writes the configuration. It reads `LOCALSTACK_AUTH_TOKEN` from the environment or prompts for the required token.

Set `LOCALSTACK_AUTH_TOKEN`. Every tool in the server requires a LocalStack Auth Token, and the setup wizard reads this variable or requests the token interactively.

It supports CDK, Terraform, and SAM deployments through `cdklocal`, `tflocal`, and `samlocal`. The applicable wrapper must be installed and available on the system path, and deployments can use parameters and variables.

Yes, Cursor is named as a compatible MCP client. The README also names Claude and VS Code, while the initialization wizard detects installed clients and writes their configuration.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLocalstack MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/localstack-localstack-mcp-server?style=directory)](https://allmcps.com/mcp/localstack-localstack-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/localstack-localstack-mcp-server"><img src="https://allmcps.com/api/badge/localstack-localstack-mcp-server?style=directory" alt="Localstack MCP Server on AllMCPs" /></a>