Fusion Schema MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Fusion Schema MCP Servershow columns for the FND_USER table"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Tool | Purpose |
| FTS over name + description + module; discovery by description |
| metadata: type, module, description, primary key, column count |
| columns with type/size/nullable/description/PK flag |
| exists? + fuzzy "did-you-mean" (EBS→Fusion drift) |
| per-column exists + suggestions |
| indexes with ordered columns + uniqueness |
| declared FKs + mined relationships, tagged + confidence = join paths |
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 the split seed DBs schema.sqlite + reports.sqlite (FTS5 + lookup indexes).
Boot
The container starts through /entry (setup V1 task 9): it waits for the stack.fusion module on
the oservices-setup Config API (SETUP_URL), logs [entry] stack.fusion rev=N and
[entry] stack.fusion CATALOG_VERSION=<v|(unset)>, reports its status, then execs
/entrypoint.sh unchanged (the CATALOG_DB gate below still applies). A standalone build needs
the named build context: docker build --build-context oservices-config=../oservices-setup/config ..
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 schema.sqlite + reports.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.shDocker (the shipping form)
docker compose build
docker compose up -d
curl http://localhost:8979/healthThe image is code + the bge-small model cache ONLY — no catalog data is compiled or baked
(since 2026-09-25). CATALOG_DB is REQUIRED from the deployment (no image default):
postgres(dev):DATABASE_URL→ thefusiondatabase onstack-db; nothing SQLite is touched and nothing is written under/app.sqlite:DATA_DIR+SEED_DIR— a seed VOLUME carryingVERSION+schema.sqlite.zip+reports.sqlite.zip(built on a dev box withnpm run compile && npm run zip-seed); on startentrypoint.shrunsprovision.js, which unpacks/upgrades the split DBs inDATA_DIR. A missing seed file is a loud boot failure, never an empty catalog. A pre-split singlecatalog.sqliteis converted once withnode dist/migrate-split.js <catalog.sqlite> --schema <dir>/schema.sqlite --reports <dir>/reports.sqlite.
Connecting an agent
Point any MCP client at the Streamable-HTTP endpoint:
http://<host>:8979/mcpe.g. Claude Agent SDK / Codex SDK mcpServers config, or the MCP inspector.
Env
Var | Default | Meaning |
|
| HTTP port |
|
| bind host |
| — (required) |
|
| — (required, postgres) | the |
| — (required, sqlite) | dir holding the split DBs; also the source CSV/JSON dir for the dev-box compile step |
|
| schema tables (tables/columns/keys/relationships/meta) |
|
| report corpus (report_queries + fts + vec) |
|
| column-search embedding cache |
| — (required, sqlite) | seed volume: |
|
| smoke-client target |
This server cannot be deployed
Maintenance
Related MCP Connectors
List datasets, schemas, run APL queries, and use prompts for exploration, anomalies, and monitoring.
PostgreSQL, MySQL, OpenAPI/Swagger, and shared Agent Memory with scoped access.
Astra DB tools for agents: schema, find, vector search, guarded writes, and interactive views.
Shared, permission-aware company context for AI agents, with provenance, approvals and audit.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides contextual Oracle database schema information to AI assistants, enabling them to understand and work with large databases containing thousands of tables. Supports multi-database connections, smart schema caching, table lookups, and relationship mapping.-
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with Oracle Databases by providing specific table and column metadata as context. Users can generate SQL statements and retrieve query results directly through natural language prompts.Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to interactively interrogate database schema metadata using SchemaCrawler.12-
- FlicenseNot gradedqualityBmaintenanceEnables read-only exploration of Oracle databases through natural language, providing schema inspection and safe bounded SQL query execution.-