Oracle Database MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | info |
| ORACLE_USER | Yes | Oracle database username (should be read-only user) | |
| ORACLE_PASSWORD | Yes | Oracle database password | |
| ORACLE_POOL_MAX | No | Maximum number of connections in the pool | 10 |
| ORACLE_POOL_MIN | No | Minimum number of connections in the pool | 2 |
| MAX_QUERY_LENGTH | No | Maximum length of SQL query | 50000 |
| QUERY_TIMEOUT_MS | No | Query timeout in milliseconds | 30000 |
| MAX_ROWS_PER_QUERY | No | Maximum number of rows to return per query | 1000 |
| ENABLE_AUDIT_LOGGING | No | Enable audit logging of queries | true |
| ORACLE_CONNECTION_STRING | Yes | Oracle database connection string in format hostname:port/servicename |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_databaseA | Execute a read-only SQL SELECT query against the Oracle database. Returns rows, column names, and execution metrics. |
| get_database_schemaA | Get database schema information. If tableName is provided, returns column details for that table. Otherwise, returns a list of all accessible tables. |
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 2 tools
The two tools have clearly distinct purposes: get_database_schema retrieves metadata about the database structure, while query_database executes SQL queries for data retrieval. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun naming pattern (get_database_schema, query_database) with clear, descriptive names that align with their functions. The naming is uniform and predictable.
With only 2 tools, the server feels under-scoped for an Oracle Database MCP Server, as it lacks essential operations like data manipulation (INSERT, UPDATE, DELETE), transaction management, or administrative tasks, making it incomplete for typical database workflows.
The tool surface is severely incomplete for a database server, covering only schema inspection and read-only queries. Missing are critical operations such as data modification, stored procedure execution, user management, and other core database functionalities, leading to significant gaps.