Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Dynobase

by Dynobaseversion 1.0.0i★ –iRuns on your computer
Registry nameio.github.Dynobase/dynobase-mcp

Install

Overview

Description from the maker (original English)

Query DynamoDB from AI tools through the Dynobase desktop app. Read-only unless you allow writes.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Download the maker’s .mcpb file

The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.

Run this in your terminal

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Dynobase, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32602 servers in this category
  • Published to the registry more recently than 88% of the other 32602 servers in this category
  • Basic checks equal to or better than 100% of the other 32602 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Dynobase safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Rystic

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

Rystic

by Rystic-Inc

Start, seed, clock, inspect and diff Rystic API simulators from your agent.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

dynobase-mcp

This package connects AI tools that only launch stdio MCP servers, such as Claude Desktop, Codex and Windsurf, to the MCP server built into Dynobase, the desktop client for Amazon DynamoDB.

Dynobase 3.0 and later can run a Model Context Protocol server on your machine. AI tools can use it to list your tables, read their schemas and query your data through the AWS profiles Dynobase has loaded. It is read-only unless you allow writes. Claude Code and Cursor can connect to it over HTTP directly.

This package bridges every other client to it. It reads MCP messages on stdin, forwards them to Dynobase, and writes the answers to stdout. It has no dependencies.

The bridge is MIT-licensed. Dynobase itself is a paid app with a 7-day free trial.

Requirements

  • Dynobase 3.0 or later, open, with Settings → AI → MCP server turned on
  • Node.js 18 or later. The Claude Desktop extension doesn't need it, because Claude Desktop includes Node.js on macOS and Windows.

Setup

Turn on the MCP server in Dynobase, then add the bridge to your client. The bridge reads the port and token from Dynobase's settings, so your client config doesn't need the token.

Claude Desktop extension: download the .mcpb file from the latest release and open it. Claude Desktop shows an install dialog. Leave the token and URL fields empty.

Claude Desktop (manual config), Windsurf and other clients with an `mcpServers` file

{

"mcpServers": { "dynobase": { "command": "npx", "args": ["-y", "github:Dynobase/dynobase-mcp"] } } }

Codex (~/.codex/config.toml)

[mcp_servers.dynobase]

command = "npx" args = ["-y", "github:Dynobase/dynobase-mcp"]

Claude Code also works with the bridge:

claude mcp add dynobase -- npx -y github:Dynobase/dynobase-mcp

Claude Code and Cursor can also skip the bridge and connect to Dynobase over HTTP. Dynobase's settings section shows the snippets for that.

To test the connection from a terminal:

npx -y github:Dynobase/dynobase-mcp --check

Options

FlagEnvironment variableDefault
--url DYNOBASE_MCP_URLhttp://127.0.0.1: /mcp, using the port saved in Dynobase (41961 unless you changed it)
--token DYNOBASE_MCP_TOKENThe token saved in Dynobase's settings

Flags take precedence over environment variables, and environment variables take precedence over Dynobase's settings.

Dynobase saves its settings in ~/.dynobase, or in DYNOBASE_DATA_DIR if that's set. If the bridge can't read that folder, for example because the client runs as a different user, pass the token explicitly.

What your AI tool can do

These read tools are always available:

ToolWhat it does
list_profilesLists loaded profiles with their regions and table names
list_tablesLists the table names of one profile
describe_tableReturns the full DescribeTable output plus TTL
scanReturns one page of a Scan
queryReturns one page of a Query
get_itemReturns one item by primary key
partiqlRuns one PartiQL statement, SELECT only unless writes are allowed
explain_querySays which index a key condition would use, and whether it's a Query or a Scan

The write tools are put_item, update_item, delete_item, batch_write and PartiQL writes. They only work after you turn on Allow writes in Dynobase. Dynobase records each write an MCP client makes in the item's History, so you can revert it. PartiQL writes are the exception: they can't be reverted.

Each call returns up to about 1 MB of items and times out after 60 seconds. The tools come from your installed version of Dynobase, not from this package.

Security

  • Dynobase's MCP server listens on 127.0.0.1 only. It rejects requests whose Host header isn't a loopback name.
  • Every request needs the bearer token. The bridge reads the token from your own settings folder, sends it only to the configured URL, and never logs it.
  • The server is read-only unless you allow writes.
  • Your AWS credentials stay in Dynobase. Clients only see tool results.

Troubleshooting

npx -y github:Dynobase/dynobase-mcp --check reports what it finds. The bridge writes its logs to stderr, which most clients show in their MCP logs.

  • "Can't reach Dynobase": open Dynobase and check that Settings → AI → MCP server is on. If you changed the port, the bridge reads the new one from the settings, unless you set --url or DYNOBASE_MCP_URL.
  • "The MCP server is turned off in Dynobase": turn it on in Settings → AI → MCP server.
  • "Dynobase rejected the token": the token was regenerated. Update --token or DYNOBASE_MCP_TOKEN, or remove them so the bridge reads the current token from the settings.

How it works

Each line on stdin is one JSON-RPC message. The bridge POSTs it to Dynobase's Streamable HTTP endpoint with Authorization: Bearer . It then writes each JSON-RPC message in the answer to stdout, one per line. Answers can be JSON or an event stream, and requests run in parallel.

Some errors happen before Dynobase answers, such as a refused connection or a rejected token. The bridge returns those as JSON-RPC errors that say how to fix them.

License

MIT. Dynobase is a separate commercial product: https://dynobase.dev

Ask PopNx