Custom MCP Database

Name: Custom MCP Database
Author: renanlido

by renanlidoversion 0.6.2i★ –iRuns on your computer

Registry nameio.github.renanlido/custom-mcp-database

Install

Overview

Description from the maker (original English)

Run alias-based queries against PostgreSQL, MySQL, MongoDB and Oracle without exposing credentials.

PopNx MCP’s three pillars

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

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

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: Databases & datasets

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.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "custom-database": {
      "command": "uvx",
      "args": [
        "custom-mcp-database"
      ]
    }
  }
}

Run this in your terminal

claude mcp add custom-database -- uvx custom-mcp-database

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "custom-database": {
      "command": "uvx",
      "args": [
        "custom-mcp-database"
      ]
    }
  }
}

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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "custom-database": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "custom-mcp-database"
      ]
    }
  }
}

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 renanlido, 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 Databases & datasetsi

More stars than 0% of the other 957 servers in this category
Published to the registry more recently than 16% of the other 957 servers in this category
Basic checks equal to or better than 100% of the other 957 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 Custom MCP Database 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 (0.6.2) reached the registry 5 months ago.

Which apps can use it?

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

What can I use instead?

In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server

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

Supabase

by supabase

Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.

Computer or cloud★ 2,993Apache-2.0Updated yesterday

Install

MongoDB MCP Server

by mongodb-js

MongoDB Model Context Protocol Server

Runs on your computer★ 1,157Apache-2.0Updated 3 days ago

Install

Elasticsearch MCP Server

by cr7258

MCP server for interacting with Elasticsearch

Runs on your computer★ 315Apache-2.0Updated 14 months ago

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.

Custom MCP Database

mcp-name: io.github.renanlido/custom-mcp-database

An MCP server that lets AI agents run alias-based queries against PostgreSQL, MySQL, MongoDB and Oracle — without ever exposing credentials to the model. Connections are configured once and stored locally; the agent only ever references them by alias.

Works with Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Gemini CLI, and any other MCP client (all use the same stdio launch command).

Quickstart

There are two roles, on purpose. Keeping them separate is what stops your DB password from ever reaching the model.

You (once, in your terminal) — install the credentials

The agent never installs credentials. You do, with the CLI. The secret stays on your machine and is never sent to the model.

Easiest way — the guided wizard (asks type, host, user, and how to supply the secret; optionally tests the connection):

uvx custom-mcp-database setup

Or do it in one line (you'll be prompted for the password — hidden input):

uvx custom-mcp-database add-db --alias prod_ro --type postgres \

--host db.internal --port 5432 --user reporting --dbname app

uvx custom-mcp-database list-aliases # confirm it's there

The agent (always) — uses it by alias

Point your MCP client at the server (see Install), then just ask:

"Using prod_ro, run SELECT count(*) FROM orders."

The agent calls db_execute_query with the alias prod_ro — never a host, user, or password. It physically cannot see the credentials; they live in your local config, resolved only inside the server process at query time.

Why the agent can't add the DB: an MCP tool's arguments are produced and read by the LLM. If the agent typed your password into an add tool, that password would land in the model's context, the provider, and the logs. So credential setup is a human/CLI step by design. (Need an agent to wire connections in an automated pipeline? See MCP_DB_ALLOW_ADMIN_TOOLS in SECURITY.md — even then it only accepts a *reference* to a secret, e.g. an env-var name, never the secret itself.)

Writes are off by default (read-only). To allow them for a task: export MCP_DB_READONLY=0 MCP_DB_ALLOW_WRITES=1.

Install

The server runs over stdio. The universal launch command is uvx custom-mcp-database run (requires uv; the package is fetched from PyPI on first run).

Claude Code

# Direct (published package)

claude mcp add custom-mcp-database -- uvx custom-mcp-database run

Or install the full plugin from this repo's marketplace

/plugin marketplace add renanlido/custom-mcp-database /plugin install custom-mcp-database@renanlido-mcp

Claude Desktop

Two options:

One-click bundle — build the .mcpb (mcpb pack) and open it in Claude Desktop. See Distribution.
Manual config — add the snippet from examples/mcp-clients/claude-desktop.json to claude_desktop_config.json.

Other clients

Copy the matching snippet — all use the same command/args, only the file and key differ:

Client	Config file	Key	Snippet
Cursor	`~/.cursor/mcp.json`	`mcpServers`	cursor.json
VS Code	`.vscode/mcp.json`	`servers`	vscode.json
Windsurf	`~/.codeium/windsurf/mcp_config.json`	`mcpServers`	windsurf.json
Gemini CLI	`~/.gemini/settings.json`	`mcpServers`	gemini-cli.json

Full client matrix and a local-checkout variant: examples/mcp-clients/README.md.

Configure connections

Configure connections from your terminal with the CLI — never through the agent. A connection's password is a real secret; if it were passed as an MCP tool argument it would enter the model's context (and the provider, transcripts, and logs). So the credential-management tools are off the MCP surface by default; provisioning is a human/CLI task. The agent only lists and uses aliases.

Omit --password/--uri to be prompted securely (hidden input, not stored in shell history). Even better, keep the secret out of the config file entirely with --password-env / --password-file (resolved at connection time):

# PostgreSQL — prompted for the password (recommended)

uvx custom-mcp-database add-db --alias pg --type postgres \ --host localhost --port 5432 --user me --dbname app

MySQL — password taken from an env var at connect time (nothing secret on disk)

MYSQL_PW=... uvx custom-mcp-database add-db --alias my --type mysql \ --host localhost --port 3306 --user root --dbname app --password-env MYSQL_PW

Oracle — password read from a file (e.g. a mounted secret)

uvx custom-mcp-database add-db --alias ora --type oracle \ --host db.example.com --port 1521 --user system --dbname ORCLPDB1 \ --password-file /run/secrets/ora_pw

MongoDB — full URI from a file (the URI embeds credentials)

uvx custom-mcp-database add-db --alias mongo --type mongo \ --dbname app --uri-file /run/secrets/mongo_uri

uvx custom-mcp-database list-aliases uvx custom-mcp-database remove-db --alias pg

Config location (override with MCP_DB_CONFIG): $XDG_CONFIG_HOME/custom-mcp-database/mcp_config.sqlite3 (default ~/.config/custom-mcp-database/mcp_config.sqlite3, 0600).

If you pass a literal --password/--uri, it is stored as plaintext JSON in that

SQLite file. Prefer --password-env/--password-file (or --uri-env/--uri-file) so

only a reference is stored. Either way, keep the file secret (it is 0600, gitignored,

not encrypted).

MCP tools

Tool	Purpose
`db_list_aliases`	List configured aliases and types
`db_execute_query`	Run SQL or a MongoDB JSON filter
`db_list_collections`	List MongoDB collections
`db_security_status`	Report the active security policy

db_add_database / db_remove_database are not exposed over MCP by default — manage connections with the CLI. To opt into exposing them (the add tool only accepts secrets by reference, never a literal password), set MCP_DB_ALLOW_ADMIN_TOOLS=1.

db_execute_query notes: SQL runs as given with parameterized binds (add your own LIMIT); MongoDB takes a JSON filter + collection, caps results at 10 (--limit), rejects empty filters, and coerces 24-char hex strings to ObjectId.

Security

This server handles real credentials and production data, so it ships deny-by-default:

Read-only by default. Only SELECT-class SQL runs. Writes/DDL require explicit opt-in.
No stacked statements (;-injection blocked), single statement per call.
MongoDB server-side JavaScript blocked ($where, $function, $accumulator, mapReduce, …).
Identifiers validated (oracle_schema can't be used for injection).
Results capped at MCP_DB_MAX_ROWS (default 1000); secrets redacted from errors.
Credential store is 0600 plaintext SQLite — keep the host disk encrypted.

Check the live posture: custom-mcp-database security-status (or the db_security_status tool).

Enable writes for a specific task (then turn it back off):

export MCP_DB_READONLY=0

export MCP_DB_ALLOW_WRITES=1 # INSERT/UPDATE/DELETE

export MCP_DB_ALLOW_DDL=1 # only if you really need CREATE/DROP/ALTER/...

Read the full protocol — least-privilege DB roles, TLS, prompt-injection handling, vulnerability reporting — in [SECURITY.md](SECURITY.md). The app-layer guards are defense-in-depth; the authoritative control is a least-privilege database account.

Develop

uv sync                 # create .venv and install deps

make run # run the server (stdio) make lint # ruff make build # sdist + wheel into dist/

Inspect tools interactively:

uv run mcp dev src/custom_mcp_database/server.py

Distribution

This repo ships ready-to-publish metadata for every major channel. All of it is published automatically on push to main (see below):

Channel	File	Published by
PyPI	`pyproject.toml`	`release.yml` (push to main)
MCP Registry	`server.json`	`release.yml` (push to main)
Claude Code plugin	`.claude-plugin/plugin.json`, `.mcp.json`	available on GitHub push
Claude Code marketplace	`.claude-plugin/marketplace.json`	available on GitHub push
Claude Desktop bundle	`manifest.json`	`release.yml` attaches `.mcpb` to the Release

Automated release — just push to `main`

Releases are fully automated. On every push to main, .github/workflows/release.yml:

Picks the next semantic version from your commits since the last tag (feat: → minor, BREAKING CHANGE/type!: → major, anything else → patch; add [skip release] to a commit message to skip).
Writes that version into pyproject.toml and syncs it into every artifact (server.json, manifest.json, plugin + marketplace) via scripts/sync_version.py — version lives in one place, no hand-bumping.
Builds, commits chore(release): vX [skip ci], tags vX, pushes.
Publishes to PyPI (Trusted Publishing/OIDC), then the MCP Registry (GitHub OIDC).
Packs the `.mcpb` and cuts a GitHub Release with the wheel + bundle attached.

The release commit carries [skip ci], so it does not re-trigger the workflow.

One-time setup (can't be automated — needs your accounts):

Create a PyPI Trusted Publisher for renanlido/custom-mcp-database, workflow release.yml.
Allow GitHub Actions to push to main (repo → Settings → Actions → *Read and write permissions*; if main is a protected branch, allow the actions bot to bypass or use a PAT).

The MCP Registry namespace is io.github.renanlido/custom-mcp-database (GitHub-validated).

Local manual escape hatch: make build (syncs version + builds) then uv publish.

License

MIT

Custom MCP Database

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Databases & datasetsi

Common questions

Alternatives

Supabase

MongoDB MCP Server

Elasticsearch MCP Server

README from the maker

Custom MCP Database

Quickstart

You (once, in your terminal) — install the credentials

The agent (always) — uses it by alias

Install

Claude Code

Or install the full plugin from this repo's marketplace

Claude Desktop

Other clients

Configure connections

MySQL — password taken from an env var at connect time (nothing secret on disk)

Oracle — password read from a file (e.g. a mounted secret)

MongoDB — full URI from a file (the URI embeds credentials)

MCP tools

Security

export MCP_DB_ALLOW_DDL=1 # only if you really need CREATE/DROP/ALTER/...

Develop

Distribution

Automated release — just push to main

License

Automated release — just push to `main`