# localstack/localstack-mcp-server [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/localstack/localstack-mcp-server  
**GitHub Stars:** 29  
**npm Downloads (last month):** 885  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/localstack-localstack-mcp-server

## Description
A MCP server for LocalStack to manage local AWS environments, including lifecycle operations, infra deployments, log analysis, fault injection, and state management.

## Tools
Capabilities this server exposes over MCP:

- **localstack-app-inspector** — Query and manage App Inspector traces, spans, and events to review deployed LocalStack applications
- **localstack-aws-client** — Executes an AWS CLI command against the running LocalStack container using the 'awslocal' wrapper.
- **localstack-aws-replicator** — Replicate external AWS resources into a running LocalStack instance using the AWS Replicator HTTP API.
- **localstack-chaos-injector** — Injects, manages, and clears chaos faults and network effects in LocalStack to test system resilience.
- **localstack-cloud-pods** — Manages remote LocalStack Cloud Pods with following actions: save, load, delete
- **localstack-deployer** — Deploys or destroys AWS infrastructure on LocalStack using CDK, Terraform, or SAM.
- **localstack-docs** — Search the LocalStack documentation to find guides, API references, and configuration details
- **localstack-ephemeral-instances** — Manage cloud-hosted LocalStack Ephemeral Instances: create, list, fetch logs, and delete.
- **localstack-extensions** — Install, uninstall, list, and discover LocalStack Extensions from the marketplace
- **localstack-iam-policy-analyzer** — Configures LocalStack's IAM enforcement and analyzes logs to automatically generate missing IAM policies.
- **localstack-logs-analysis** — LocalStack log analyzer that helps developers quickly diagnose issues and understand their LocalStack interactions
- **localstack-management** — Manage LocalStack lifecycle: start, stop, restart, or check status
- **localstack-snowflake-client** — Execute SQL queries and commands against the LocalStack Snowflake emulator using the Snowflake CLI (snow). Use this to run SELECT queries, DDL (CREATE/DROP), DML (INSERT/UPDATE/DELETE), SHOW DATABASES/SCHEMAS/TABLES, DESCRIBE TABLE, and any other Snowflake SQL.
- **localstack-state-management** — Export, import, reset, and inspect LocalStack state using local file-based workflows on disk.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

**Requires environment variables:** `LOCALSTACK_AUTH_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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:

```bash
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.

_Full upstream README: https://allmcps.com/mcp/localstack-localstack-mcp-server/readme_