Supabase
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Description from the maker (original English)
An Oracle MCP server built from the PL/SQL, tables and statements you select. No run-sql tool
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
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": {
"mcpdbwizard": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/srmadscience/mcpdbwizard:2.0.29"
]
}
}
}Run this in your terminal
claude mcp add mcpdbwizard -- docker run -i --rm ghcr.io/srmadscience/mcpdbwizard:2.0.29Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mcpdbwizard": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/srmadscience/mcpdbwizard:2.0.29"
]
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"mcpdbwizard": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/srmadscience/mcpdbwizard:2.0.29"
]
}
}
}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.
Runs on your computer; the tool list appears in your AI app after you install it.
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 6, 2026
The registry name was verified with the GitHub account srmadscience, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (2.0.29) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
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’s official server lets AI create tables, query data and review project settings in your Supabase database.
MongoDB Model Context Protocol Server
MCP server for interacting with Elasticsearch
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.
An MCP server for Oracle, built from the objects you choose. Tick the PL/SQL packages, tables, sequences and your own tested SQL statements in a console, and it generates a Model Context Protocol server exposing exactly those to an AI agent as typed tools — each carrying a JSON Schema derived from the procedure's real signature.
There is no `run-sql` tool. Anything you did not select has no tool, no method and no class: it is absent from the binary rather than refused at run time. Nothing composes a query at run time either — the generated code is ordinary Java with fixed SQL statements and typed binds, and the MCP server calls those wrappers rather than writing SQL for a model to run.
Generating that server means generating the whole calling layer, so you get it too: typed DAO factories, callable-statement wrappers, table managers and an optional SOAP layer. They are useful on their own, but the MCP server is the point.
Supports Oracle 12c through 26ai, and is regression-tested against six live instances spanning that range.
*How the full product fits together. This repository is the generator — the config file, generate & compile, and the generated MCP server. The Design pages, Runtime page and proxy are the web console in the Docker image; here you select objects with the Swing tool or a config file instead, and the generated server can be run on its own.*
The usual way round is to hand the agent a run-sql tool, and it works until the schema is real: published text‑to‑SQL accuracy falls sharply on enterprise‑scale schemas compared with tidy benchmarks, and a wrong UPDATE is not a wrong answer, it is an incident.
The alternative is curated tools — but writing one per procedure by hand does not scale past a few, and PL/SQL is unusually hostile to deriving them automatically:
This project does that derivation. Every generated MCP tool carries a real JSON Schema built from the procedure's actual signature, so the agent is *told* what the parameters are rather than inferring them from prose.
oracle: PROCEDURE order_summary(p_customer IN NUMBER,
p_totals OUT summary_rec, p_lines OUT SYS_REFCURSOR)
tool: order_summary { "p_customer": } -> { "p_totals": { "orderCount": 12, "value": 4210.55 }, "p_lines": [ { "sku": "AB-1", "qty": 3 }, ... ] }
A record crosses as a JSON object, a REF CURSOR as an array of row objects, a DATE as an ISO‑8601 string, RAW and binary vectors as base64, CLOB as text, BLOB as base64.
Requires Java 21 and Maven. The Oracle JDBC driver (com.oracle.database.jdbc:ojdbc11) comes from Maven Central — nothing to install by hand.
mvn clean package
That produces two jars in target/: a plain one, and a self‑contained mcpdbwizard-app- -shaded.jar with the driver bundled.
# Interactive (Swing) -- pick objects and options, save a config
java -jar target/mcpdbwizard-app-*-shaded.jar myconfig.pb2
java -jar target/mcpdbwizard-app-*-shaded.jar build myconfig.pb2
is created if missing.
Changed in 2026-08: there used to be a leading
argument. It has been
removed, and a command line that still passes one will be read as the log directory.
It was validated for shape only — ≥19 characters, not a path, not the literal
build—
and then ignored, so it authenticated nothing. Drop it from any script that supplies it.
Configs are .pb2 (a flat properties file) or .json; both are accepted, and convert losslessly either way:
java -cp target/mcpdbwizard-app-*-shaded.jar \
com.mcpdbwizard.schema.ConfigConverter myconfig.pb2 myconfig.json
| DAO factory | one entry point per config, wiring connections and logging |
| PL/SQL wrappers | a class per procedure/function — setParamX, executeProc, getParamY |
| Table managers | row CRUD by primary key, plus unique‑key, index and foreign‑key‑child lookups |
| SQL statement classes | your own SQL, with typed bind parameters |
| SOAP service layer | optional |
| JSON / JSON‑RPC connectors | optional |
| MCP server | optional (needs Java 17+ for the MCP SDK) |
Generated code depends only on com.mcpdbwizard.pub, the runtime library in this repository.
A single generated McpServer.java, speaking stdio by default or Streamable HTTP when started with http [port]. Optional bearer‑token auth and TLS both read their secrets from the environment at run time and fail closed if unset, so no secret is baked into the generated source.
It exposes PL/SQL routines, table row CRUD and secondary lookups, user SQL statements, sequences, and — on 23ai — JSON‑relational duality views with document CRUD and etag optimistic locking.
What is exposed is decided when you generate, not at run time. An object you did not select has no code generated for it at all, and TABLE_MCP_CRUD_ narrows a table to any subset of create/read/update/delete. An operation that is not exposed has no tool method emitted — it is absent from the binary, not merely unregistered.
Beyond the ordinary scalars and LOBs: 12c identity columns and extended VARCHAR2/RAW; 21c native JSON; 23ai native BOOLEAN, VECTOR (dense, binary and sparse), and JSON‑relational duality views.
Known gaps: TIMESTAMP WITH [LOCAL] TIME ZONE and BFILE cross as procedure parameters but not yet as table columns; SDO_GEOMETRY has no JSON mapping, so a routine using one is skipped; FLOAT16 vectors are blocked server‑side.
Generated factories pick a LogInterface implementation from the config: console, text file, java.util.logging, Log4j 1.x, SLF4J, or Log4j 2. The SLF4J and Log4j 2 backends live in com.mcpdbwizard.pub and depend only on the facade jar, which is an optional dependency — supply the api plus a binding yourself if you use them.
The database‑free suite needs nothing and is green on a fresh clone:
mvn test
Tests that need Oracle are gated: with no database reachable they *skip* rather than fail. To point them at your own instance, copy the templates — the real files are gitignored and never leave your machine:
cp src/test/resources/test-boxes.properties.template src/test/resources/test-boxes.properties
cp Scripts/tns/tnsnames.ora.template Scripts/tns/tnsnames.ora cp Scripts/boxes.env.template Scripts/boxes.env
Per setting, an environment variable (MCPDBWIZARD_TEST_HOST, …) always wins over the file, which is how a run selects one server over another.
A third tier links against generator output: Scripts/testrun_current.sh regenerates code from a set of configs and compiles it, and a family of harnesses then drives that code against a live database.
That tier is not part of this repository, and neither are the schemas it needs. The configs introspect Oracle schemas whose structure is not ours to publish — some of it came from customer work years ago — and a config *enumerates* the schema it points at, so the configs cannot ship either. The harnesses go with them: they name those schemas' tables and routines, and they only compile against a regenerated tree that cannot exist here.
What that costs you: nothing to run the generator, and nothing to run the suite. The database-free tests are complete and green on a fresh clone; the gated live tests skip. What you do not get is a ready-made corpus to regenerate against. Scripts/check_provisioning.sh stays, and will name the exact objects a config expects, which is the place to start if you build your own.
examples/generated-output/ shows what the generator emits, with no database at all.
| Path | What |
|---|---|
src/main/java/com/mcpdbwizard/pub | runtime library the generated code links against |
src/main/java/com/mcpdbwizard/app | the generator — engine, Swing UI, shared helpers |
src/main/java/com/mcpdbwizard/schema | typed model of a config; .pb2 ↔ .json |
src/main/java/com/mcpdbwizard/mcpdbwizardconnector | JSON / JSON‑RPC connector generator |
examples/generated-output | a checked‑in example of generator output, regenerated 2026‑08‑07 |
Scripts/ | regeneration, provisioning checks, and the export gate |
| API docs | generated javadoc for com.mcpdbwizard.pub, the library you link against |
Contributor notes — architecture, conventions and accumulated gotchas — are in CLAUDE.md.
[API docs for `com.mcpdbwizard.pub`](https://srmadscience.github.io/mcpdbwizard-open/)
That is the runtime library generated code links against, and the only package documented — the generator's own internals are implementation, and publishing them would bury the part you call. The package summary explains what to reach for, and carries the compatibility contract: signatures there are load-bearing for every program this generator has produced, so they gain methods and do not change them.
The same pages are on the project site at mcpdbwizard.com/javadoc. Both are regenerated from source on publish rather than copied from one another.
Locally, mvn javadoc:javadoc writes them to target/reports/apidocs/. It runs with failOnWarnings, so a broken @link fails the build rather than shipping a dead cross-reference.
[Known issues](https://mcpdbwizard.com/docs/known-issues/) — what is wrong, what a caller actually sees when it bites, and the workaround for each. Most of them do not announce themselves: a record whose JSON keys are the generated field names rather than the column names, a VECTOR routine parameter that takes a dense array only, a config whose tool count outgrows Oracle's open_cursors.
Every open entry there is also an issue in this repository, linked from the page. Read it before filing — and if one of them is biting you, say so on its issue rather than opening a new one. Three of those entries are documented rather than fixed *because nobody has asked*, so a comment is the whole difference between "nobody has ever needed this" and "somebody does".
See CONTRIBUTING.md. One thing to run before opening a pull request:
Scripts/export/check-export-clean.sh
It fails if a private hostname, a credential or a jar has crept into the tree.
Please report a suspected vulnerability privately, not in a public issue — see SECURITY.md.
Apache License 2.0 — see LICENSE and NOTICE.
Code this generator *emits* is your own work and carrie
Only the beginning is shown; read the rest in the repo