dynoxide MCP Server
nubo-db/dynoxide
[](https://agentrank-ai.com/tool/nubo-db--dynoxide/?utm_source=badge&utm_medium=readme&utm_campaign=agentrank_badge) A DynamoDB emulator in Rust, backed by SQLite. Starts in milliseconds as a single static binary, and is verified against real AWS by a public conformance suite. Runs as an HTTP server, an MCP server for coding agents, an embeddable library, or in the browser via WebAssembly.
claude mcp add agentrank -- npx -y agentrank-mcp-server Overview
nubo-db/dynoxide is a Rust MCP server licensed under Apache-2.0. A DynamoDB emulator in Rust, backed by SQLite. Starts in milliseconds as a single static binary, and is verified against real AWS by a public conformance suite. Runs as an HTTP server, an MCP server for coding agents, an embeddable library, or in the browser via WebAssembly. Topics: aws, database, dynamodb, dynamodb-local, mcp, rust, sqlite, testing, conformance, dynamodb-emulator, ci, dynalite, emulator, localstack, webassembly.
Ranked #888 out of 24846 indexed tools.
In the top 4% of all indexed tools.
Ecosystem
Score Breakdown
100 stars → early stage
Last commit 1mo ago → moderate activity
91/112 issues closed → responsive maintainer
7 contributors → small team
No dependents → no downstream usage
Weights: Freshness 20% · Issue Health 20% · Dependents 22% · Stars 10% · Contributors 8% · How we score →
Matched Queries
From the README
# Dynoxide
A DynamoDB emulator in Rust, backed by SQLite. Runs as an HTTP server or an MCP server for coding agents, embeds into Rust and iOS applications as a library, and compiles to WebAssembly for the browser.
> The crates.io badge above shows the **crate** version, which covers the Rust library alone. Everything you install rather than depend on carries a separate **product** version: the binary, the npm packages, the container images, the browser engine and the Action. That is the number `dynoxide --version` prints and the one to quote in a bug report. [Why there are two](docs/versioning.md).
## Why Dynoxide?
I built Dynoxide because DynamoDB Local is slow, heavy, and can't embed. It needs a JVM, and the typical Docker-based setups adds ~3 seconds of cold-start, ~209 MB of memory at idle, and a ~225MB Docker image (~473 MB on disk) before you've done anything useful. If you're running integration tests, that's Docker starting, the JVM warming up, and your pipeline waiti Read full README on GitHub → Get the weekly AgentRank digest
Top movers, new tools, ecosystem insights — straight to your inbox.