Writing ·
Oracle ships its own MCP server. When should you use ours instead?
Oracle has put MCP into its own tooling: SQLcl can run as an MCP server, there is an OCI Database Tools MCP server for managed cloud deployments, and ORDS exposes an MCP endpoint over HTTPS. If you have been told “Oracle already does this”, that is what they mean, and it is true.
So let me be straight about it: SQLcl’s MCP server is good, and for a lot of people it is the right answer. It is also solving a different problem to ours, and the difference is worth understanding before you pick.
What SQLcl MCP is for
It is a developer and DBA tool. It runs locally, it uses the credentials already on your machine, and
it gives the model a run-sql tool so it can execute SQL and PL/SQL against your database.
For exploratory work that is exactly what you want. You are sitting there. You can see what it did. You already have the privileges it is using, so it cannot reach anything you could not have reached yourself, and if it writes a daft query you notice immediately and say so.
That loop — a person, their own credentials, immediate feedback — is where an unconstrained SQL tool is genuinely appropriate. I would use it for that.
Where that model stops working
Change three things and it stops fitting.
Nobody is watching. The agent is running as part of an application, on a schedule, or on behalf of a customer. There is no person to notice the daft query.
The credentials are not the caller’s. The server connects as one account, and whoever is calling inherits everything that account can do. “It can only do what the user can do” is no longer true, because there is no user.
Somebody has to sign it off. Once it is production, someone will ask what this thing is able to do to the database, and the answer needs to be a list rather than a description of good intentions.
At that point a run-sql tool is the wrong shape — not because it is badly built, but because its
whole design assumes a human in the loop who is no longer there.
What we do instead
MCP DB Wizard generates a server from a list you curate: specific PL/SQL packages and procedures,
specific tables with specific operations, specific SQL statements you wrote and tested. Those become
typed tools. There is no run-sql tool, because no such tool is generated.
The list is the security model. It is also a file you can review, version and diff.
Use both, honestly
These are not really competitors. A sensible setup is SQLcl MCP on developer laptops for exploration, and a curated generated server for anything an application or a customer touches. The first is a power tool for people who already have the keys. The second is what you hand to something that doesn’t.
If you only need the first, use Oracle’s — it is free, it is supported, and it ships with tools you already have.
How do I get MCP DB Wizard?
It’s available from our GitHub repo as a Docker image. It supports Oracle 12c through 26ai, and is regression-tested against six live instances spanning that range.