Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Localstack MCP Server

by localstackversion 0.5.0i★ –iRuns on your computer
Registry nameio.github.localstack/localstack-mcp-server

Install

Overview

Description from the maker (original English)

A LocalStack MCP Server providing essential tools for local cloud development & testing

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: LOCALSTACK_AUTH_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, AWS_REPLICATOR_SOURCE_AWS_ACCESS_KEY_ID, AWS_REPLICATOR_SOURCE_AWS_SECRET_ACCESS_KEY, AWS_REPLICATOR_SOURCE_AWS_SESSION_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: LOCALSTACK_AUTH_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, AWS_DEFAULT_REGION, AWS_REPLICATOR_SOURCE_AWS_ACCESS_KEY_ID, AWS_REPLICATOR_SOURCE_AWS_SECRET_ACCESS_KEY, AWS_REPLICATOR_SOURCE_AWS_SESSION_TOKEN, AWS_REPLICATOR_SOURCE_REGION_NAME, AWS_REPLICATOR_SOURCE_ENDPOINT_URL, APP_INSPECTOR

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "localstack": {
      "command": "npx",
      "args": [
        "-y",
        "@localstack/localstack-mcp-server"
      ],
      "env": {
        "LOCALSTACK_AUTH_TOKEN": "your-value",
        "AWS_ACCESS_KEY_ID": "your-value",
        "AWS_SECRET_ACCESS_KEY": "your-value",
        "AWS_SESSION_TOKEN": "your-value",
        "AWS_DEFAULT_REGION": "your-value",
        "AWS_REPLICATOR_SOURCE_AWS_ACCESS_KEY_ID": "your-value",
        "AWS_REPLICATOR_SOURCE_AWS_SECRET_ACCESS_KEY": "your-value",
        "AWS_REPLICATOR_SOURCE_AWS_SESSION_TOKEN": "your-value",
        "AWS_REPLICATOR_SOURCE_REGION_NAME": "your-value",
        "AWS_REPLICATOR_SOURCE_ENDPOINT_URL": "your-value",
        "APP_INSPECTOR": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add localstack --env LOCALSTACK_AUTH_TOKEN=your-value --env AWS_ACCESS_KEY_ID=your-value --env AWS_SECRET_ACCESS_KEY=your-value --env AWS_SESSION_TOKEN=your-value --env AWS_DEFAULT_REGION=your-value --env AWS_REPLICATOR_SOURCE_AWS_ACCESS_KEY_ID=your-value --env AWS_REPLICATOR_SOURCE_AWS_SECRET_ACCESS_KEY=your-value --env AWS_REPLICATOR_SOURCE_AWS_SESSION_TOKEN=your-value --env AWS_REPLICATOR_SOURCE_REGION_NAME=your-value --env AWS_REPLICATOR_SOURCE_ENDPOINT_URL=your-value --env APP_INSPECTOR=your-value -- npx -y @localstack/localstack-mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "localstack": {
      "command": "npx",
      "args": [
        "-y",
        "@localstack/localstack-mcp-server"
      ],
      "env": {
        "LOCALSTACK_AUTH_TOKEN": "your-value",
        "AWS_ACCESS_KEY_ID": "your-value",
        "AWS_SECRET_ACCESS_KEY": "your-value",
        "AWS_SESSION_TOKEN": "your-value",
        "AWS_DEFAULT_REGION": "your-value",
        "AWS_REPLICATOR_SOURCE_AWS_ACCESS_KEY_ID": "your-value",
        "AWS_REPLICATOR_SOURCE_AWS_SECRET_ACCESS_KEY": "your-value",
        "AWS_REPLICATOR_SOURCE_AWS_SESSION_TOKEN": "your-value",
        "AWS_REPLICATOR_SOURCE_REGION_NAME": "your-value",
        "AWS_REPLICATOR_SOURCE_ENDPOINT_URL": "your-value",
        "APP_INSPECTOR": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "localstack": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@localstack/localstack-mcp-server"
      ],
      "env": {
        "LOCALSTACK_AUTH_TOKEN": "your-value",
        "AWS_ACCESS_KEY_ID": "your-value",
        "AWS_SECRET_ACCESS_KEY": "your-value",
        "AWS_SESSION_TOKEN": "your-value",
        "AWS_DEFAULT_REGION": "your-value",
        "AWS_REPLICATOR_SOURCE_AWS_ACCESS_KEY_ID": "your-value",
        "AWS_REPLICATOR_SOURCE_AWS_SECRET_ACCESS_KEY": "your-value",
        "AWS_REPLICATOR_SOURCE_AWS_SESSION_TOKEN": "your-value",
        "AWS_REPLICATOR_SOURCE_REGION_NAME": "your-value",
        "AWS_REPLICATOR_SOURCE_ENDPOINT_URL": "your-value",
        "APP_INSPECTOR": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • LOCALSTACK_AUTH_TOKEN secret required env
    LocalStack Auth Token (required for all LocalStack MCP tools)
  • AWS_ACCESS_KEY_ID secret env
    Source AWS access key used by AWS Replicator to read external AWS resources
  • AWS_SECRET_ACCESS_KEY secret env
    Source AWS secret access key used by AWS Replicator to read external AWS resources
  • AWS_SESSION_TOKEN secret env
    Optional source AWS session token used by AWS Replicator for temporary credentials
  • AWS_DEFAULT_REGION env
    Source AWS region used by AWS Replicator
  • AWS_REPLICATOR_SOURCE_AWS_ACCESS_KEY_ID secret env
    Optional Replicator-specific source AWS access key. Use this instead of AWS_ACCESS_KEY_ID when the Replicator source account should be isolated from generic AWS config.
  • AWS_REPLICATOR_SOURCE_AWS_SECRET_ACCESS_KEY secret env
    Optional Replicator-specific source AWS secret access key. Use with AWS_REPLICATOR_SOURCE_AWS_ACCESS_KEY_ID.
  • AWS_REPLICATOR_SOURCE_AWS_SESSION_TOKEN secret env
    Optional Replicator-specific source AWS session token for temporary credentials.
  • AWS_REPLICATOR_SOURCE_REGION_NAME env
    Optional Replicator-specific source AWS region. Use with the AWS_REPLICATOR_SOURCE_* credential group.
  • AWS_REPLICATOR_SOURCE_ENDPOINT_URL env
    Optional Replicator-specific source AWS endpoint URL for advanced source-account scenarios.
  • APP_INSPECTOR env
    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.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account localstack, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32384 servers in this category
  • Published to the registry more recently than 13% of the other 32384 servers in this category
  • Basic checks equal to or better than 100% of the other 32384 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Localstack MCP Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: LOCALSTACK_AUTH_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, AWS_REPLICATOR_SOURCE_AWS_ACCESS_KEY_ID, AWS_REPLICATOR_SOURCE_AWS_SECRET_ACCESS_KEY, AWS_REPLICATOR_SOURCE_AWS_SESSION_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.5.0) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, 오늘냥이 (Oneul Nyangi)

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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."
  • "Start the LocalStack Azure emulator, create a resource group and a storage account, and upload ./data/sample.csv to a new blob container."

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 the LocalStack for AWS, Snowflake and Azure emulators 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 NameDescriptionKey Features

| localstack-management | Manages LocalStack runtime operations for AWS, Snowflake and Azure stacks | - 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, Terraform, and SAM tooling to deploy infrastructure locally

  • Enable parameterized deployments with variable support
  • Process and present deployment results
  • 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

  • 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 remote LocalStack Cloud Pods for development workflows | - Save current state as a Cloud Pod

  • Load previously saved Cloud Pods instantly
  • Delete Cloud Pods from remote cloud-backed storage
  • Use this for managed remote state snapshots, not local export/import files
  • 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

  • Import LocalStack state from a local file
  • Inspect current LocalStack state as JSON metamodel data
  • Reset all state or only selected services
  • Supports service-level granularity for export, reset, and inspect
  • Use this for local disk workflows; use Cloud Pods for remote cloud-backed snapshots
  • Requires a valid LocalStack Auth Token |

| localstack-extensions | Installs, uninstalls, lists, and discovers LocalStack Extensions | - Manage installed extensions (list, install, uninstall) inside the running container

  • Browse the LocalStack Extensions marketplace (available)
  • 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

  • List available ephemeral instances, fetch logs, and delete instances
  • Supports lifetime, extension preload, Cloud Pod preload, and custom env vars on create
  • Requires a valid LocalStack Auth Token |

| 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-azure-client | Runs Azure CLI (`a

Only the beginning is shown; read the rest in the repo

Ask PopNx