io.github.giovanemartins/localstack vs AWS IoT Core
io.github.giovanemartins/localstack is an MCP server published by giovanemartins. Marketplaces we read that list it: 1 (Official MCP Registry). AWS IoT Core is an MCP server published by nagarjunr. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.giovanemartins/localstack |  AWS IoT Core |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.5 Downloads/month (npm): 145 Downloads/week (npm): 32 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (PyPI): 82 Downloads/week (PyPI): 22 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.giovanemartins/localstack | AWS IoT Core |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@giovane.martins/localstack) | On your machine (aws-iot-core-mcp-server) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 2 | 5, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/giovanemartins/localstack-mcp-server | github.com/nagarjunr/iot-mcp-servers |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.giovanemartins/localstack
MCP server for LocalStack AWS services, enabling AI agents to interact with local AWS infra.
AWS IoT Core
MCP server for AWS IoT Core: device registry, shadows, jobs, rules, messaging.
How to run each
io.github.giovanemartins/localstack As a local MCP server: npm package
claude mcp add --env "AWS_ACCESS_KEY_ID=<YOUR_AWS_ACCESS_KEY_ID>" --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --transport stdio localstack -- npx -y @giovane.martins/localstackRequires: AWS_ACCESS_KEY_ID (secret), AWS_SECRET_ACCESS_KEY (secret)
AWS IoT Core As a local MCP server: PyPI package
claude mcp add --env "AWS_REGION=<YOUR_AWS_REGION>" --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --env "AWS_SESSION_TOKEN=<YOUR_AWS_SESSION_TOKEN>" --transport stdio aws-iot-core -- uvx aws-iot-core-mcp-serverRequires: AWS_REGION, AWS_SECRET_ACCESS_KEY (secret), AWS_SESSION_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.giovanemartins/localstack asks for
LOCALSTACK_ENDPOINT
Only AWS IoT Core asks for
AWS_PROFILEAWS_SESSION_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.giovanemartins/localstack · What it can do: AWS IoT Core · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.