Oracle ERP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORACLE_USER | Yes | Read-only database user. | |
| MCP_MAX_ROWS | No | Default and maximum rows returned per call (max 1000). | 200 |
| ORACLE_SCHEMA | Yes | Schema exposed to the assistant (e.g. your ERP schema). | |
| ORACLE_PASSWORD | Yes | Password of that user. | |
| MCP_REPORTS_FILE | No | Path to the curated report registry. | config/reports.json |
| MCP_QUERY_TIMEOUT_MS | No | Round-trip timeout per database call. | 15000 |
| ORACLE_CONNECT_STRING | Yes | Easy Connect string, e.g. host:1521/SERVICE. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesB | List tables and views in the ERP schema with their business descriptions. |
| describe_tableA | Show columns, data types, comments, primary key and foreign keys of a table or view. Use it before writing SQL. |
| run_queryA | Execute a single Oracle SELECT/WITH statement and return at most 200 rows as JSON. Data-changing statements, PL/SQL, DB links and DBMS_/UTL_ packages are rejected. |
| list_reportsB | List curated, pre-approved ERP reports (PL/SQL procedures returning SYS_REFCURSOR) and their parameters. |
| run_reportA | Run a curated report by name. Use list_reports to see available reports and parameters. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing vs running curated reports, listing vs describing tables, and a separate ad-hoc query tool. There is no overlap between the discovery tools and the execution tools.
All five tools follow a consistent verb_noun snake_case pattern (list_reports, run_report, list_tables, describe_table, run_query). The convention is predictable throughout.
Five tools is well-scoped for a read-only ERP query/reporting interface, with each tool earning its place across discovery and execution. No redundant or trivial tools.
The surface covers the full read-only lifecycle: discover reports and tables, inspect schema, and execute both curated and ad-hoc queries. Minor gaps like pagination beyond the 200-row cap or schema search are workable but slightly limiting.