MCP Server for Oracle
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TNS_ADMIN | No | TNS admin directory | |
| ORACLE_HOME | No | Oracle client library path | |
| ORACLE_PASS | No | Legacy single-database password | |
| ORACLE_USER | No | Legacy single-database user | |
| ORACLE_CONFIG_PATH | No | Custom config file path for multi-database configuration | |
| ORACLE_CONNECTION_STRING | No | Legacy connection string |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| oracle_queryA | Run a read-only SELECT query on an Oracle database |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| oracle_usage_guide | Guide for querying Oracle databases |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Oracle Database Connections | List of available Oracle database connections with access modes |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as running read-only SELECT queries on an Oracle database, making it distinct by default.
The single tool name 'oracle_query' follows a clear and consistent verb_noun pattern (query as the action, oracle as the domain). With only one tool, there is no inconsistency to evaluate, so it scores perfectly.
One tool is too few for a database server's apparent scope, which typically requires operations like insert, update, delete, schema inspection, or transaction management. This minimal set severely limits functionality and will likely cause agent failures in complex tasks.
The tool surface is severely incomplete for an Oracle database server. It only supports read-only SELECT queries, missing essential CRUD operations (create, update, delete), schema exploration, connection management, and other database interactions, making it inadequate for typical database workflows.