Creating configs

This page is an outline. What is here is accurate, but it is not yet the whole story — each section ends with a note on what is still to be written. For anything it does not answer, DEPLOYMENT.md and USING-MCP.md in the repository are the complete references.

A config names the objects you are willing to expose. That is the whole security model, and it is a file you can review, diff and put through a change process.

An object that is not in the config has no tool, no method and no class in the generated server. It is not hidden at request time — it is absent from the binary.

The file

Configs are plain .pb2 properties or .json — the same content either way.

# payroll.pb2
MCP_SERVER=YES
MCP_HTTP_TOKEN=YES

TABLE_USER_0=PAYROLL
TABLE_NAME_0=EMPLOYEE
TABLE_MCP_CRUD_0=R

PROC_USER_0=PAYROLL
PROC_PACKAGE_0=JS_ADMIN
PROC_NAME_0=GETADMINTOOLINFO

SEQUENCE_USER_0=PAYROLL
SEQUENCE_NAME_0=JOB_ID

PASS=FROM_ENV_VARIABLE_DB_PASS

A config saved from the console never contains a password — it records the FROM_ENV_VARIABLE_DB_PASS placeholder, so there is nothing on the volume to leak.

Naming

Config names must be valid Java package names — payroll or com.example.payroll, not payroll-api. The name is a file, a directory, a path segment in /mcp/<config> and the identity the access matrix grants on, so it is limited to an alphabet all four agree about.

Use more than one

A selected table yields at least four tools, so fifty tables is two hundred before any PL/SQL. If an agent is struggling to choose, that is a curation problem. Make a second config selecting only what that agent needs.

Configs are the unit of curation and of access, so this also narrows what the calling account can reach.

Descriptions

Every tool gets a generated description carrying its columns or parameters with their Oracle types, and you can replace it with your own. The description is what the model reads when it decides whether to call a tool: say what the call does and when it applies, in plain language. Vague descriptions produce wrong tool choices far more often than bad parameters do.

To write. The full key reference for both formats; converting between them; version control and review workflow; what changes require a regeneration.