Documentation
Documentation
MCPDBWizard reads your Oracle schema and generates an MCP server for the objects you selected. An object you did not select has no tool, no method and no class — the curation is enforced by absence from the binary rather than by a rule at request time.
New here? Start with the Quickstart.
Getting started
Get a server running and an agent talking to it.
-
Quickstart
Run the container, select Oracle objects, generate an MCP server and connect an agent to it.
-
Launching on Docker outline
Running the MCPDBWizard container — ports, the data volume, secrets, memory limits and compose.
-
Docker parameters outline
Every environment variable the container reads, what it does, and which ones need a regeneration rather than a restart.
Oracle
The database side: the account, the connection, sessions and pooling.
-
Creating an Oracle user with minimal privileges outline
The database account an agent reaches Oracle through, and why its grants are the real security boundary.
-
Connecting to Oracle outline
How the console reaches your database — SID versus service name, the one password, and what happens when it cannot.
-
Session management outline
What a generated server tells Oracle about itself, how to find its sessions in V$SESSION and its SQL in V$SQL, and when a transaction ends.
-
Connection pooling outline
Give each concurrent caller its own DAO factory instead of queueing them all on one connection — and size it against the database, not the CPU.
Operating
Running it for real — logs, audit records, metrics and accounts.
-
Setting up logging outline
Where the console and generated servers write, what one tool call looks like in the log, and how to point logging somewhere else.
-
Setting up auditing outline
A durable, replayable record of every tool call — the sink, what it records, and the write-ahead spool that survives an outage.
-
Setting up metrics and Grafana outline
Two Prometheus endpoints, why an empty dashboard is nearly always the second one, and the label that makes the data worth having.
-
Creating application users outline
Accounts, API tokens and the access matrix — how a client proves who it is, and what it is allowed to drive.
Curating
Choosing what an agent can reach. This is the security model.
-
Creating configs outline
The config file is the security model — what a config is, how it is stored, and why two small ones usually beat one large one.
-
Working with procedures outline
Exposing PL/SQL routines as tools — every OUT parameter comes back, overloads never collide, and you decide who commits.
-
Working with sequences
The smallest surface in the product — one selected sequence, one tool, and nothing else.
-
Working with tables outline
Read operations by primary key, unique key, index and foreign key — and why insert, update and delete deserve a second thought.
-
Working with SQL statements outline
Your own curated, tested SQL, exposed as tools — how parameters get names and types, and what crosses JSON.
Beyond this site
The repository carries two long-form guides these pages summarise:
DEPLOYMENT.md for the operator's side and
USING-MCP.md for the caller's, with every request and response
taken from a live server. Where a page here disagrees with those, they are
right and the page is a bug.