localstack

The LocalStack MCP Server exposes a set of tools to manage and interact with a LocalStack for AWS container from any MCP-enabled client. It provides commands to start, stop, restart, and monitor LocalStack, as well as utilities to deploy infrastructure (CDK and Terraform) directly to the LocalStack environment, analyze logs, generate IAM policies from violations, inject chaos for resilience testing, manage state snapshots through Cloud Pods, and handle LocalStack Extensions. With this MCP server, you can securely automate common LocalStack operations via MCP-compatible tooling and AI-assisted workflows, enabling streamlined local cloud development and testing.

To use the server, install the MCP package (via npx in this configuration) and run the server in your MCP-enabled environment. You’ll gain access to dedicated tools such as localstack-management for runtime operations and authentication, localstack-deployer for infrastructure deployments, localstack-logs-analysis for troubleshooting and insights, localstack-iam-policy-analyzer for policy remediation, and more. Each tool is designed to operate within the LocalStack container context, supporting token-based authentication, environment variable injection, and service-specific targeting to help you build, test, and safeguard local cloud environments.

Prerequisites:

• Node.js (if using the npx/Node flow) or an environment capable of running MCP servers
• Access to the internet to fetch the MCP server package via npx
• Optional: LocalStack Auth Token for enhanced features

Installation steps:

1. Ensure Node.js is installed on your machine.
   • Verify: node -v and npm -v
2. Install and run the MCP server via npx using the package name (as per the configuration):
   • npx -y localstack-mcp-server
3. If prompted, provide or configure your LocalStack Auth Token and any required environment variables.
4. Verify the server starts and exposes its MCP endpoints for your MCP client to connect.

Notes:

• The exact package name used by npx may vary; if the package is renamed, adjust the command accordingly.
• If you prefer a non-npx approach, you can install the package locally and run the server using the appropriate node command as per the package documentation.

Tips and considerations:

• Some features require an active LocalStack Auth Token; ensure your token is valid and configured in the environment variables (e.g., LOCALSTACK_AUTH_TOKEN).
• The server includes a suite of tools (management, deployer, logs-analysis, IAM policy analyzer, chaos injector, cloud pods, extensions, AWS client, docs) for comprehensive LocalStack operations—each tool has its own capability set and requirements.
• If you encounter token or permission errors, verify that the MCP client has the correct scopes and that the LocalStack container is accessible from your network.
• For troubleshooting, consult the Logs Analysis tool to summarize errors and filter by service or operation; ensure you have the appropriate network rules to reach LocalStack endpoints.
• When using deployment tools, ensure CDK Local or Terraform Local are installed in your environment if required by your deployment workflow.