Dynoxide MCP server
io.github.nubo-db/dynoxide·v1.5.0·95 starsA DynamoDB emulator with an MCP server exposing 35 DynamoDB tools to coding agents.
not scanned yet
95 stars6.8k downloads/wk
Reviews
Write oneNobody has reviewed Dynoxide yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Dynoxide tools
No tool declarations could be read from the package source. They show once the server is installed.
How Dynoxide compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 85% of 48,255 servers
- GitHub stars
- 95
- more than 95% of 28,688 servers
- Downloads a week
- 6,834
- more than 95% of 12,191 servers with a package
Release history: 4 versions in the registry since 2026-09-14, latest 2026-10-23, typically one every 13 days.
Install Dynoxide in Claude Code, Cursor or VS Code
Runs npx -y dynoxide on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add dynoxide -- npx -y dynoxide
What the publisher says
From the Dynoxide repository's README, as published. We do not edit it. Read it on GitHub
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.
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 <!-- prose:ddblocalcoldstart -->2–3 seconds<!-- /bench --> of cold-start, <!-- prose:ddblocalidlememory -->~205 MB<!-- /bench --> of memory at idle, and a <!-- prose:ddblocalimagesize -->~225MB<!-- /bench --> Docker image (<!-- prose:ddblocalimagesize_disk -->~473 MB<!-- /bench --> 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 waiting.
Dynoxide is a native binary. It starts in milliseconds, idles at <!-- prose:dynoxideidlememory -->~5.3 MB<!-- /bench -->, and ships as a <!-- prose:dynoxidebinarysize -->~3 MB<!-- /bench --> download. Point any DynamoDB SDK at it and your tests just work.
For Rust projects, there's also an embedded mode - direct API calls via Database::memory() with no HTTP layer at all. Each test gets an isolated in-memory database with zero startup cost. And because it compiles to a native library with no runtime dependencies, it runs on platforms where DynamoDB Local can't, including iOS.
Performance
Local Development (Apple Silicon)
CI (GitHub Actions)
Numbers from ubuntu-latest (<!-- prose:cirunnerhardware -->4-core Intel(R) Xeon(R) 6973P-C, 16GB RAM<!-- /bench -->). Commit <!-- bench:cicommitlink_root -->49c6338<!-- /bench -->.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Dynoxide: common questions
- Is Dynoxide MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the Dynoxide safety report
- How do I install Dynoxide?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Dynoxide need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Dynoxide maintained?
- The last commit was 36 days ago (2026-09-29). The latest release is v1.5.0.
- How does Dynoxide compare with other MCP servers?
- safety score 91/100 (higher than 85% of 48,255 servers); github stars 95 (more than 95% of 28,688 servers); downloads a week 6,834 (more than 95% of 12,191 servers with a package). Full comparison.