Fusion Schema MCP Server

Standalone HTTP MCP server that grounds a Fusion-SQL agent against the Oracle Fusion schema catalog. The models already know most Oracle ERP names (from EBS on-prem), but Fusion Cloud ≠ EBS — so these tools validate and correct the objects/columns the agent thinks it knows, and surface real join paths (declared FKs + mined relationships).

Scope: grounding only. No SQL parsing, no SQL execution/validation (that needs a live Oracle DB — later round). No agent, no CloudBeaver UI (later rounds).

Tools

Related MCP server: OracleDB MCP Server

Data

data/ holds the source metadata (copied from ../../Bip/DB_SCHEMA via scripts/copy-data.sh): META_TABLES/COLUMNS/INDEXES/PKEYS/FKEYS.csv + mined_relationships.json. The compile step filters junk table rows to TABLE/VIEW and builds catalog.sqlite (FTS5 + lookup indexes).

Build & run (CloudBeaver WSL distro)

All commands run inside the CloudBeaver WSL distro. Scripts avoid PowerShell→wsl quoting.

# 1. copy source data into ./data (once)
bash scripts/copy-data.sh

# 2. install deps, build TS, compile catalog.sqlite
bash scripts/install-build-compile.sh

# 3. boot + live smoke test (starts server, runs a real MCP client, asserts acceptance criteria)
bash scripts/verify.sh

Docker (the shipping form)

docker compose build
docker compose up -d
curl http://localhost:8979/health

The multi-stage image compiles the catalog at build time and ships only dist/ + catalog.sqlite (the 250MB CSVs are dropped from the runtime image).

Connecting an agent

Point any MCP client at the Streamable-HTTP endpoint:

http://<host>:8979/mcp

e.g. Claude Agent SDK / Codex SDK mcpServers config, or the MCP inspector.

Env