Skip to main content
Glama
Oracle Database MCP Server

Oracle Database MCP Server

by monsterygy

Oracle Database MCP Server — Production Edition

A production-grade Model Context Protocol (MCP) server for Oracle database interaction, providing 11 tools for full CRUD, transactions, execution plans, and comprehensive safety guardrails.

拿来即用 — 无需 clone、无需手动 build。配置好 mcp.json 就能用。

Features

11 Tools

Tool

Purpose

Read/Write

Safety

db_health_check

Verify driver & connection diagnostics

Read

—

db_list_tns

Parse tnsnames.ora aliases

Read

—

db_list_tables

List all tables (optional schema filter)

Read

—

db_describe_table

Get column schema of a table

Read

—

db_query

Execute read-only SQL (SELECT/WITH)

Read

Read-only enforced

db_explain_plan

Preview execution plan without running

Read

—

db_insert

Insert a record (with dry_run)

Write

Identifier validation

db_update

Update records matching WHERE (with dry_run)

Write

Safety row cap

db_delete

Delete records matching WHERE (with dry_run)

Write

Safety row cap

db_transaction

Multi-step atomic transaction

Write

All-or-nothing

db_session_info

Current session/privilege info

Read

—

Production-Grade Features

  • Centralized config validation — Fails fast on missing env vars at startup

  • Structured logging — Request IDs, log levels (DEBUG/INFO/WARN/ERROR), JSON or text format

  • Custom error types — ConnectionError, QueryError, ValidationError, TimeoutError, RateLimitError, AccessDeniedError with error codes

  • Rate limiting — Sliding window, configurable per-minute cap

  • Connection retry — Exponential backoff for transient failures (ORA-03113, TNS errors)

  • Pool resilience — Health check, dead connection detection, automatic reinitialization

  • Table whitelist/blacklist — Configurable table-level access control

  • Read-only mode — Optional flag to block all DML operations

  • DML safety cap — Pre-counts matching rows, refuses if exceeding DML_MAX_ROWS

  • Dry-run mode — Preview generated SQL without executing for INSERT/UPDATE/DELETE

  • Oracle type conversion — DATE, TIMESTAMP, CLOB, BLOB → JSON-serializable values

  • SQL injection prevention — Parameterized binds, identifier validation, multi-statement blocking

  • Big-number precision guard — Rejects numeric binds beyond 2^53 - 1 (silent JS precision loss); pass big integers as strings instead

  • ROWID-based insert fetch — db_insert returns the inserted row via ROWID, immune to big-number key corruption

  • Unit tested — 55 unit tests + 18 offline protocol tests covering all security boundary functions


Related MCP server: MCP Oracle Server

Quick Start

三种方式,按需选择:

方式一:GitHub npx(最简单,推荐给同事)

无需 clone、无需手动 build。prepare 脚本会自动编译。

npx -y github:monsterygy/oracle-mcp-server

MCP 客户端配置(同事拿到这段 JSON 填上账号密码即可):

{
  "mcpServers": {
    "oracle-db": {
      "command": "npx",
      "args": ["-y", "github:monsterygy/oracle-mcp-server"],
      "env": {
        "ORACLE_USER": "hr",
        "ORACLE_PASSWORD": "yourpass",
        "ORACLE_CONNECT_STRING": "localhost:1521/ORCLPDB1"
      }
    }
  }
}

首次启动会从 GitHub 下载并自动编译(约 30 秒),之后使用缓存秒启。

方式二:离线 Tarball(适合内网/无外网环境)

打包(你执行一次,生成 .tgz 文件):

cd database-mcp-server
npm pack
# → 生成 gy-oracle-database-mcp-server-3.1.0.tgz(约 45KB)

安装(同事拿到 .tgz 文件后执行):

npm install -g gy-oracle-database-mcp-server-3.1.0.tgz
# → 全局安装,gy-oracle-mcp-server 命令可用

MCP 客户端配置(使用全局安装的命令,无需 npx):

{
  "mcpServers": {
    "oracle-db": {
      "command": "gy-oracle-mcp-server",
      "env": {
        "ORACLE_USER": "hr",
        "ORACLE_PASSWORD": "yourpass",
        "ORACLE_CONNECT_STRING": "localhost:1521/ORCLPDB1"
      }
    }
  }
}

方式三:Clone & Build(开发调试用)

git clone https://github.com/monsterygy/oracle-mcp-server.git
cd oracle-mcp-server
npm install      # prepare 脚本自动 build
npm start

本地路径方式配置:

{
  "mcpServers": {
    "oracle-db": {
      "command": "node",
      "args": ["/absolute/path/to/oracle-mcp-server/dist/index.js"],
      "env": {
        "ORACLE_USER": "hr",
        "ORACLE_PASSWORD": "yourpass",
        "ORACLE_CONNECT_STRING": "localhost:1521/ORCLPDB1"
      }
    }
  }
}

Integrate with MCP Clients

WorkBuddy / ccswitch

Add to ~/.workbuddy/mcp.json:

{
  "mcpServers": {
    "oracle-db": {
      "command": "npx",
      "args": ["-y", "github:monsterygy/oracle-mcp-server"],
      "env": {
        "ORACLE_USER": "hr",
        "ORACLE_PASSWORD": "yourpass",
        "ORACLE_CONNECT_STRING": "localhost:1521/ORCLPDB1",
        "LOG_LEVEL": "INFO",
        "DML_MAX_ROWS": "1000"
      }
    }
  }
}

After saving, open the connector management page and click Trust to enable.

Claude Desktop

Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "oracle-db": {
      "command": "npx",
      "args": ["-y", "github:monsterygy/oracle-mcp-server"],
      "env": {
        "ORACLE_USER": "hr",
        "ORACLE_PASSWORD": "yourpass",
        "ORACLE_CONNECT_STRING": "localhost:1521/ORCLPDB1"
      }
    }
  }
}

Cursor / VS Code (with MCP support)

Add to .cursor/mcp.json or VS Code MCP settings:

{
  "mcpServers": {
    "oracle-db": {
      "command": "npx",
      "args": ["-y", "github:monsterygy/oracle-mcp-server"],
      "env": {
        "ORACLE_USER": "hr",
        "ORACLE_PASSWORD": "yourpass",
        "ORACLE_CONNECT_STRING": "localhost:1521/ORCLPDB1"
      }
    }
  }
}

Debug with MCP Inspector

npx @modelcontextprotocol/inspector npx -y github:monsterygy/oracle-mcp-server

Or with a local clone:

npm run inspector

Configuration

All configuration is managed via environment variables. See .env.example for the full list.

Minimum Required

ORACLE_USER=hr
ORACLE_PASSWORD=your_password
ORACLE_CONNECT_STRING=localhost:1521/ORCLPDB1

Connection Methods

Method 1: EZ Connect (simplest)

ORACLE_CONNECT_STRING=localhost:1521/ORCLPDB1

Method 2: TNS Alias

ORACLE_CONNECT_STRING=ORCLPDB1
TNS_ADMIN=/path/to/oracle/network/admin

Method 3: Full TNS Descriptor

ORACLE_CONNECT_STRING=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ORCLPDB1)))

Driver Modes

Mode

Requirement

Use When

Thin (default)

None (pure JS)

Oracle 12.1+

Thick

Oracle Instant Client

Oracle 11g, advanced features

To use thick mode:

ORACLE_CLIENT_DIR=/path/to/instantclient_19_22

Safety Configuration

# Query limits
QUERY_MAX_ROWS=500           # Max rows returned by db_query
QUERY_TIMEOUT_MS=10000       # Query timeout in ms
DML_MAX_ROWS=1000            # Max rows DML can affect (safety cap)

# Access control
ALLOWED_TABLES=USERS,ORDERS # Whitelist (comma-separated, uppercase)
BLOCKED_TABLES=AUDIT_LOG    # Blacklist
READ_ONLY_MODE=false        # Block all DML if true

# Rate limiting
RATE_LIMIT_ENABLED=true
RATE_LIMIT_PER_MINUTE=60

# Logging
LOG_LEVEL=INFO               # DEBUG | INFO | WARN | ERROR | NONE
LOG_JSON=false              # JSON-structured logs if true

Docker

Quick Start with Oracle XE

docker-compose up -d

This starts:

  • Oracle XE 21c (gvenzl/oracle-xe:21-slim) on port 1521

  • MCP server connected to the Oracle XE instance

Custom Oracle Instance

docker build -t oracle-mcp-server .
docker run -i --rm \
  -e ORACLE_USER=hr \
  -e ORACLE_PASSWORD=yourpass \
  -e ORACLE_CONNECT_STRING=your-host:1521/your-service \
  oracle-mcp-server

Security Architecture

Request → [Rate Limiter] → [Zod Input Validation] → [Identifier Validation]
  → [Table Whitelist/Blacklist] → [Read-Only Check (for DML)]
  → [DML Safety Cap (pre-count)] → [Bind Variables (:1, :2)]
  → [Query Timeout] → [Row Limit (FETCH FIRST)] → Oracle DB

Security Layer

Implementation

Defends Against

Zod schema validation

.strict() + constraints

Invalid input, missing params

Identifier regex

^[a-zA-Z_][a-zA-Z0-9_]{0,127}$

SQL injection via table/column names

Table whitelist/blacklist

ALLOWED_TABLES / BLOCKED_TABLES

Unauthorized table access

Read-only enforcement

Regex check for SELECT/WITH only

DML/DDL in db_query

Multi-statement blocking

Semicolon detection

Statement injection

Parameterized binds

:1, :2 / named binds

SQL injection in values

Bind precision guard

assertSafeBindValues (BIND_PRECISION_ERROR)

Silent data corruption for numeric binds beyond 2^53 - 1

DML safety cap

Pre-count + DML_MAX_ROWS

Mass UPDATE/DELETE

Query timeout

Promise.race with timer

Slow queries

Row limit

FETCH FIRST n ROWS ONLY

Result set overflow

Rate limiting

Sliding window

Abuse / DoS

Big-Number Precision Guard (bind safety)

JavaScript numbers are IEEE-754 doubles — any integer with an absolute value above 2^53 - 1 (9007199254740991) is silently rounded to the nearest representable value before it ever reaches Oracle. Oracle NUMBER keeps up to 38 decimal digits exact, so a bind like 9007199254740993 arrives as 9007199254740992 and corrupts the data.

The server enforces a bind precision guard (assertSafeBindValues) on every tool that accepts bind values (db_query, db_insert, db_update, db_delete, db_transaction, db_explain_plan). Unsafe numeric binds are rejected with error code BIND_PRECISION_ERROR instead of being sent to the database.

The fix: pass big integers as strings — Oracle converts them to NUMBER with full precision:

// ❌ silently corrupts: 9007199254740992 is written
{ "id": 9007199254740993 }

// ✅ exact: Oracle stores 9007199254740993
{ "id": "9007199254740993" }

ROWID Usage

db_insert fetches the inserted row back via ROWID (result.lastRowid), the physical row locator Oracle assigns to the newly inserted row:

SELECT * FROM <TABLE> WHERE ROWID = :rowid_val

Fetching by ROWID is the only reliable way to return the exact row just inserted — re-selecting by a numeric key is unsafe when the key exceeds 2^53 (see the precision guard above).

ROWID caveats (so repairs are never built on false assumptions):

  • ROWID is a physical locator, not a logical key — it can change after ALTER TABLE ... MOVE, partition operations, EXPORT/IMPORT, Flashback, or table reorganization.

  • ROWIDs are only meaningful in the database/session that produced them.

  • Repairing rows already corrupted by the 2^53 bug: locate the affected rows by ROWID (from a SELECT result or a previous db_insert/db_query response) and rewrite the big-number columns in a single transaction — never re-identify by the corrupted numeric key itself.

Development

# Run in dev mode with auto-reload
npm run dev

# Lint
npm run lint

Testing

Three layers of testing are provided:

1. Unit Tests (55 tests, no DB needed)

Tests pure security functions: isReadOnlyQuery, validateIdentifier, applyRowLimit, isTableAllowed, parseTnsAliasesContent, assertSafeBindValues (big-number precision guard), buildRowidSelectSql (ROWID fetch SQL).

npm test                    # Run all unit tests
npm run test:watch         # Watch mode (re-runs on file change)
npm run test:coverage       # With coverage report

2. Offline Protocol Tests (18 tests, no DB needed)

Tests the full MCP JSON-RPC handshake, tool listing, and safety guardrails (SQL injection rejection, input validation, dry-run mode) — all without an Oracle database.

npm run test:offline

This launches the MCP server with fake credentials and verifies:

  • JSON-RPC initialize handshake succeeds

  • tools/list returns all 11 tools with inputSchema

  • db_query rejects INSERT/DROP/multi-statement injection

  • db_insert rejects SQL-injected column names

  • db_update/db_delete reject missing WHERE clauses

  • db_insert dry-run returns SQL without executing

  • db_query rejects max_rows > 500 (Zod validation)

  • db_query / db_insert reject numeric binds beyond 2^53 (BIND_PRECISION_ERROR, no DB needed)

  • string-form big-number binds pass the precision guard

  • db_health_check returns structured diagnostics even on connection failure

3. End-to-End Tests (requires Oracle DB)

Sends real JSON-RPC tool calls to the MCP server connected to your Oracle database.

# Set env vars first
export ORACLE_USER=hr
export ORACLE_PASSWORD=yourpass
export ORACLE_CONNECT_STRING=localhost:1521/ORCLPDB1

# Run full e2e test suite
npm run test:e2e

# Or test a single tool
node scripts/test-mcp.mjs db_health_check
node scripts/test-mcp.mjs db_list_tables
node scripts/test-mcp.mjs db_query "SELECT * FROM dual"

# Or just list all available tools
node scripts/test-mcp.mjs list

4. MCP Inspector (interactive GUI)

npx @modelcontextprotocol/inspector npx -y github:monsterygy/oracle-mcp-server

Opens a web UI at http://localhost:5173 where you can:

  • View all 11 tool schemas

  • Call any tool with custom parameters

  • See raw JSON-RPC request/response

  • Debug connection issues

Project Structure

oracle-mcp-server/
├── src/
│   ├── config.ts          # Centralized config validation
│   ├── logger.ts          # Structured logging with request IDs
│   ├── errors.ts          # Custom error types with codes
│   ├── rateLimiter.ts     # Sliding window rate limiter
│   ├── security.ts        # Pure security functions (unit-tested)
│   ├── db.ts              # Oracle connection pool & query execution
│   ├── index.ts           # MCP server & tool registration
│   └── __tests__/
│       └── security.test.ts  # 42 unit tests
├── scripts/
│   ├── test-offline.mjs   # 15 offline protocol tests (no DB)
│   ├── test-mcp.mjs       # End-to-end tests (requires DB)
│   └── test-github-npx.mjs # GitHub npx verification test
├── Dockerfile             # Multi-stage build
├── docker-compose.yml    # Oracle XE + MCP server
├── .eslintrc.json        # Code quality rules
├── .env.example          # Configuration template
└── package.json

Local Sharing (npm pack)

Generate a shareable tarball for colleagues (no npm registry needed):

npm pack
# → gy-oracle-database-mcp-server-3.1.0.tgz (≈45KB)

Colleagues install it:

npm install -g gy-oracle-database-mcp-server-3.1.0.tgz
# → gy-oracle-mcp-server 命令全局可用

License

MIT

Available Tools

11 tools
db_deleteDelete recordsA
Destructive

Delete one or more records from an Oracle database table using parameterized named binds.

Safety features:

  • WHERE clause is REQUIRED (deletes without conditions are blocked)

  • Pre-counts matching rows and refuses if exceeding DML_MAX_ROWS (default: 1000)

  • dry_run mode previews SQL + affected row count

Example: table_name: "users" where: "id = :w_1 AND status = :w_2" where_params: [42, "inactive"] dry_run: false

NameRequiredDescriptionDefault
whereYesWHERE clause with named bind variables (:w_1, :w_2, ...). Example: 'id = :w_1'
dry_runNoIf true, return the generated SQL and affected row count without executing.
table_nameYesTarget table name
where_paramsYesValues for :w_1, :w_2, ... in order.
db_describe_tableDescribe table schemaA
Read-onlyIdempotent

Get the column structure of a specific Oracle table: column names, data types, data lengths, nullable flag, and default values.

Use this after db_list_tables to understand a table's schema before writing queries.

Args:

  • table_name (string): The table name to inspect (case-insensitive)

  • owner (string, optional): Schema/owner name for cross-schema access

NameRequiredDescriptionDefault
ownerNoOptional: schema/owner of the table (case-insensitive). Use when the table is in another schema.
table_nameYesName of the table to describe (e.g., 'users', 'orders'). Case-insensitive — will be uppercased.
db_explain_planPreview execution planA
Read-onlyIdempotent

Generate and display the execution plan for a SQL query WITHOUT executing it.

Uses Oracle's EXPLAIN PLAN to show how the query optimizer would run the query: table access methods (FULL SCAN, INDEX RANGE SCAN, etc.), join strategies, and filter predicates.

Use this to understand query performance before running expensive queries.

Args:

  • sql (string): Read-only SQL (SELECT/WITH only) to analyze

  • params (array): Bind variable values (default: [])

NameRequiredDescriptionDefault
sqlYesA read-only SQL query (SELECT or WITH) to analyze. Must not contain DML/DDL.
paramsNoParameter values for :1, :2, ... bind variables.
db_health_checkHealth check: verify driver & connectionA
Read-onlyIdempotent

Verify that the Oracle driver is loaded correctly and the database connection is working.

Reports: oracledb driver version, driver mode (thin/thick), connection status, Oracle DB version, connect string, TNS config, pool stats, and available TNS aliases.

Use this tool FIRST when setting up the MCP server or when troubleshooting connection issues.

No parameters required.

NameRequiredDescriptionDefault

No parameters

db_insertInsert a recordA

Insert a single record into an Oracle database table using parameterized named binds.

Auto-generates an INSERT with named bind variables from the provided data object. Column names are validated to prevent SQL injection. After insert, the full row is fetched back via ROWID.

dry_run mode: Set dry_run=true to preview the generated SQL without executing it.

Example: table_name: "users" data: { "name": "Alice", "email": "alice@example.com", "active": true } dry_run: false

Args:

  • table_name (string): Target table name

  • data (object): Column-value pairs to insert

  • dry_run (boolean): Preview SQL without executing (default: false)

NameRequiredDescriptionDefault
dataYesColumn-value pairs to insert. Example: {"name": "Alice", "age": 30, "active": true}
dry_runNoIf true, return the generated SQL without executing it. Useful for previewing before committing changes.
table_nameYesTarget table name (e.g., 'users'). Oracle names are uppercase by default.
db_list_tablesList database tablesA
Read-onlyIdempotent

List all tables in the connected Oracle database (excluding system schemas like SYS, SYSTEM, etc.).

Use this FIRST to discover what tables exist before running queries.

Args:

  • owner (string, optional): Filter by schema/owner name (case-insensitive)

NameRequiredDescriptionDefault
ownerNoOptional: filter by schema/owner name (case-insensitive). E.g., 'HR', 'APP'. If omitted, lists all non-system schemas.
db_list_tnsList TNS aliases from tnsnames.oraA
Read-onlyIdempotent

Read and parse the local tnsnames.ora file, returning all available TNS alias names.

Searches in order: TNS_ADMIN directory → ORACLE_HOME/network/admin → current directory.

Args:

  • file_path (string, optional): Explicit path to tnsnames.ora.

NameRequiredDescriptionDefault
file_pathNoOptional: explicit path to a tnsnames.ora file. If omitted, auto-searches TNS_ADMIN and ORACLE_HOME/network/admin.
db_queryExecute read-only SQL queryA
Read-onlyIdempotent

Execute a read-only SQL query against the Oracle database. Only SELECT and WITH (CTE) statements are allowed.

IMPORTANT: Always use Oracle bind variables (:1, :2, ...) instead of string interpolation to prevent SQL injection.

Example: sql: "SELECT * FROM users WHERE active = :1 AND created_at > :2" params: ["Y", "2024-01-01"]

Safety:

  • Only SELECT/WITH queries allowed (INSERT/UPDATE/DELETE/DROP blocked)

  • Automatic row limit (FETCH FIRST n ROWS ONLY)

  • Query timeout enforced

  • Maximum 500 rows returned

Args:

  • sql (string): Read-only SQL with :1, :2, ... bind variables

  • params (array): Values for bind variables (default: [])

  • max_rows (number): Max rows to return (default: 100, max: 500)

NameRequiredDescriptionDefault
sqlYesA read-only SQL query. Must start with SELECT or WITH. Use Oracle bind variables :1, :2, ... for parameters.
paramsNoParameter values for :1, :2, ... bind variables. ALWAYS use these instead of string interpolation to prevent SQL injection.
max_rowsNoMaximum rows to return (default: 100). Results beyond this are truncated.
db_session_infoGet current session infoA
Read-onlyIdempotent

Retrieve information about the current database session: connected user, schema, instance name, host, database name and version, session ID, NLS date format.

Useful for verifying which database/schema you're connected to and for debugging NLS-related issues.

No parameters required.

NameRequiredDescriptionDefault

No parameters

db_transactionExecute multi-step transactionA
Destructive

Execute multiple DML statements (INSERT/UPDATE/DELETE) in a single atomic transaction.

All steps either succeed and commit together, or fail and roll back together. This ensures data consistency for multi-step operations.

Limits: 1-10 steps per transaction. Each step must use Oracle bind variables (:1, :2, ...) — never string interpolation.

Example: steps: [ { sql: "UPDATE accounts SET balance = balance - :1 WHERE id = :2", params: [100, 1] }, { sql: "UPDATE accounts SET balance = balance + :1 WHERE id = :2", params: [100, 2] }, { sql: "INSERT INTO transfers (from_id, to_id, amount) VALUES (:1, :2, :3)", params: [1, 2, 100] } ]

This is an atomic money transfer: either all three succeed or none do.

NameRequiredDescriptionDefault
stepsYesArray of 1-10 DML steps to execute atomically. All succeed or all roll back.
db_updateUpdate recordsA
Destructive

Update one or more records in an Oracle database table using parameterized named binds.

Auto-generates the SET clause from the data object. The WHERE clause MUST include named bind variables (:w_1, :w_2, ...) with corresponding where_params.

Safety features:

  • WHERE clause is REQUIRED (updates without conditions are blocked)

  • Pre-counts matching rows and refuses if exceeding DML_MAX_ROWS (default: 1000)

  • dry_run mode previews SQL + affected row count

Example: table_name: "users" data: { "status": "active" } where: "id = :w_1" where_params: [42] dry_run: false

Args:

  • table_name, data, where, where_params, dry_run (default: false)

NameRequiredDescriptionDefault
dataYesColumn-value pairs to SET. Example: {"status": "active"}
whereYesWHERE clause with named bind variables (:w_1, :w_2, ...). Example: 'id = :w_1 AND status = :w_2'
dry_runNoIf true, return the generated SQL and affected row count without executing.
table_nameYesTarget table name
where_paramsYesValues for :w_1, :w_2, ... in order. Example: [42, 'inactive']

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 11 tool updatesv3.1.0
    • First observeddb_delete
    • First observeddb_describe_table
    • First observeddb_explain_plan
    • First observeddb_health_check
    • First observeddb_insert
    • First observeddb_list_tables
    • First observeddb_list_tns
    • First observeddb_query
    • First observeddb_session_info
    • First observeddb_transaction
    • First observeddb_update

TDQS

A4.4/5.0

Scored across 11 tools

Disambiguation5/5

Each tool has a distinct, well-defined purpose: health check, TNS listing, table listing, table description, session info, query, explain plan, insert, update, delete, and transaction. There is no functional overlap or ambiguity between tools.

Naming Consistency5/5

All tool names follow the same 'db_' prefix followed by a clear verb_noun or verb pattern (e.g., db_list_tables, db_describe_table, db_insert). The naming is fully consistent in style and convention.

Tool Count5/5

With 11 tools, the server is well-scoped for an Oracle database interface. Each tool covers a necessary operation without unnecessary redundancy or bloat.

Completeness5/5

The tool set provides complete lifecycle coverage: connection verification, schema exploration (list tables, describe), querying with explain plan, and full DML operations (insert, update, delete) plus transaction support. No obvious gaps.

Maintenance

ActivityStale
ResponsivenessNo recent community issues

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    An MCP server that connects to Oracle databases using sqlplus, enabling SQL queries, schema exploration, and DDL/DML execution through natural language.
    8
    19 npm
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    A production-grade Node.js MCP server for Oracle Database with HTTP transport, enabling SQL query execution, table listing, schema retrieval, and natural language to SQL conversion via MCP tools.
    14 npm
    1
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    MCP server for accessing Oracle databases, enabling schema exploration, query execution, and performance analysis.
    12
    MIT