MCP server for LocalStack AWS services, enabling AI agents to interact with local AWS infra.
Localstack MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for LocalStack AWS services, enabling AI agents to interact with local AWS infra.
MCP server that exposes LocalStack-managed AWS services as AI-agent tools, enabling LLMs and AI agents to interact with local AWS infrastructure during development and testing.
Once Localstack is connected, these are the calls the assistant has available:
EventBridge — The EventBridge tool exposed by this serverKinesis — The Kinesis tool exposed by this serverDynamoDB — The DynamoDB tool exposed by this serverLambda — The Lambda tool exposed by this server@giovane.martins/localstack on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 4 environment variables: LOCALSTACK_ENDPOINT, AWS_REGION, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Localstack's toolset — EventBridge, Kinesis, DynamoDB and 1 more — is a fair guide to whether it matches your workflow. It is maintained by giovanemartins; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| EventBridge | The EventBridge tool exposed by this server. |
| Kinesis | The Kinesis tool exposed by this server. |
| DynamoDB | The DynamoDB tool exposed by this server. |
| Lambda | The Lambda tool exposed by this server. |
### Using a local build
```json
{
"mcpServers": {
"localstack": {
"command": "node",
"args": ["/path/to/mcp-servers/localstack/dist/index.js"],
"env": {
"LOCALSTACK_ENDPOINT": "http://localhost:4566",
"AWS_REGION": "us-east-1",
"AWS_ACCESS_KEY_ID": "test",
"AWS_SECRET_ACCESS_KEY": "test"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LOCALSTACK_ENDPOINT | Configuration value read at startup. | Optional |
| AWS_REGION | Configuration value read at startup. | Optional |
| AWS_ACCESS_KEY_ID | Credential the server authenticates with. | Yes |
| AWS_SECRET_ACCESS_KEY | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.