Fusion MCP
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 MCP find tables related to purchase orders"
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 MCP — Oracle Fusion ERP Cloud MCP Server
A local stdio MCP server (Python, FastMCP) that gives an LLM client (Claude Desktop / Claude Code) read-only access to an Oracle Fusion / ERP Cloud database — discover objects, describe tables, read source, and run SELECT queries — all via the BI Publisher SOAP API (no direct DB connection required).
Architecture
Claude Desktop / Claude Code (MCP stdio)
│
▼
Fusion MCP Server (Python, FastMCP)
Tools ──► SQL guard ──► BIP client (requests + SOAP)
│
Catalog SQL builders (ALL_OBJECTS, ALL_TAB_COLUMNS, …)
│
▼
Oracle Fusion — BI Publisher web services
ExternalReportWSSService (runReport → base64 CSV)
│
▼
FUSION schema + ALL_* data dictionaryPrerequisites
1 — Fusion BIP service account
Create (or identify) a Fusion user that:
Has the BI Publisher role (
BIPAdministratoror a custom role with BIP access).Has read-only access on the FUSION schema and the Oracle data dictionary (
SELECT_CATALOG_ROLEequivalent, or appropriate Fusion data roles).Will be used as
FUSION_USER/FUSION_PASSWORDin.env.
This is the primary security boundary — the app-layer SQL guard enforces
SELECT/WITH only, but the BIP service account must also be read-only at
the database level.
2 — Python 3.11+
Install uv or use pip.
Setup (local development)
# Clone the repo
git clone https://github.com/ramesharavapally/FUSION-MCP.git
cd FUSION-MCP
# Install (editable + dev deps)
uv pip install -e ".[dev]"
# Copy and fill in credentials
cp .env.example .env
# Edit .env: set FUSION_BASE_URL, FUSION_USER, FUSION_PASSWORDRunning the server
# From a local clone
uv run fusion-mcp
# Or directly from GitHub without cloning (production use)
uvx --from git+https://github.com/ramesharavapally/FUSION-MCP.git fusion-mcpDeploying the SQL-runner report
The server does not deploy any BIP artifacts — you set up the report manually in the BI Publisher catalog before running the server.
The query is sent as a base64-encoded bind parameter named query1 (not a
lexical &query1). This is deliberate: passing raw SQL as a lexical value trips
BIP's SQL-injection guard (SQLInjection Error: Invalid parameter value …), and
on Fusion SaaS that guard can't be disabled. Base64-encoding keeps the parameter
value free of SQL keywords, and a PL/SQL data model decodes it and opens a cursor.
Create a CSV-output report over a data model whose dataset is this PL/SQL block:
DECLARE
TYPE refcursor IS REF CURSOR;
xdo_cursor REFCURSOR;
l_query VARCHAR2(32000);
FUNCTION get_query(p_query IN VARCHAR2) RETURN VARCHAR2 IS
BEGIN
RETURN utl_raw.cast_to_varchar2(
utl_encode.base64_decode(utl_raw.cast_to_raw(p_query)));
END;
BEGIN
l_query := get_query(:query1);
OPEN :xdo_cursor FOR l_query;
END;The server base64-encodes each query and strips any trailing ; before sending
(the decoded statement must not carry a semicolon, since it is opened as a
cursor). Then point the server at the report:
# .env
FUSION_REPORT_PATH=/your/existing/report/path.xdoTests
# Unit tests — no Fusion connection required
uv run pytest
# Single test file
uv run pytest tests/test_sql_guard.pyMCP Inspector (interactive tool testing)
npx @modelcontextprotocol/inspector uv run fusion-mcpRegister with Claude Desktop
Add to claude_desktop_config.json (typically at
%APPDATA%\Claude\claude_desktop_config.json on Windows or
~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"fusion-mcp": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/ramesharavapally/FUSION-MCP.git",
"fusion-mcp"
],
"env": {
"FUSION_BASE_URL": "https://<pod>.fa.ocs.oraclecloud.com",
"FUSION_USER": "your_bip_service_user",
"FUSION_PASSWORD": "your_password",
"FUSION_MAX_ROWS": "100",
"LOG_LEVEL": "INFO"
}
}
}
}uvx fetches the package directly from GitHub and runs it in an isolated
environment — no local clone or pip install needed. Claude Desktop
re-uses the cached environment on subsequent starts; to pick up a new
commit, restart Claude Desktop (uvx re-checks the git ref on each cold
start).
Tip: pin to a specific commit or tag for stability:
"git+https://github.com/ramesharavapally/FUSION-MCP.git@v1.0.0"
Available MCP tools
Tool | Description |
| Search |
| Find tables/views by name or comment |
| Find tables by column name or column comment |
| Full-text search across |
| Full column/PK/index/stats description of a table or view |
| Read full source of a procedure/function/package from |
| Discover argument names, types, and directions from |
| List all subprograms inside a package |
| Run a read-only |
Note:
call_procedureis not available in Fusion MCP. Oracle BIP executes SELECT data models only — anonymous PL/SQL blocks are not supported. Useget_procedure_signatureandread_object_sourcefor procedure discovery.
Security model
SQL guard (
safety/sql_guard.py) — rejects anything that is not a singleSELECT/WITH; blocks;chaining; validates identifiers used in catalog SQL. This is the app-layer boundary.BIP data model — the deployed report decodes the base64
query1bind parameter and opens it as a cursor (OPEN … FOR), which only executes a single query; multi-statement/DML text cannot be smuggled through this path.Service account — the BIP user should have read-only database grants (see prerequisites above). This is the ultimate security boundary.
Configuration reference
Variable | Default | Description |
| — | Fusion pod URL, e.g. |
| — | BIP service account username |
| — | BIP service account password |
|
| BIP catalog path for the manually-deployed report |
|
| Maximum rows returned per query |
|
| HTTP timeout for BIP calls (seconds) |
|
| Logging level (DEBUG, INFO, WARNING, ERROR) |
Available Tools
9 toolsdescribe_tableA
Full description of a Fusion table or view:
columns (name, type, length/precision, nullable, default, comment)
primary key columns
indexes (name, type, uniqueness, columns)
table-level comment
estimated row count from optimizer stats
owner: schema owner, e.g. 'FUSION' table_name: exact table name, e.g. 'AP_INVOICES_ALL'
Inputs: owner (required), table_name (required).
execute_queryA
Execute a read-only SELECT or WITH (CTE) query against the Oracle Fusion database via BI Publisher.
Only SELECT/WITH statements are accepted — DML, DDL, and PL/SQL are rejected. SQL is executed through the BIP SQL-runner report (deployed manually in the BIP catalog; see FUSION_REPORT_PATH).
sql: the full query text with literal values inlined (BIP does not support bind variables — include values directly, e.g. WHERE org_id = 101) max_rows: maximum rows to return (server cap also applies)
Returns: {columns: [...], rows: [{col: val, ...}, ...], count: N} Note: all values are returned as strings (CSV transport).
Inputs: sql (required), max_rows.
get_procedure_signatureA
Return the full argument list for a stored procedure or function (from ALL_ARGUMENTS). Returns: argument_name, data_type, in_out, position, defaulted, default_value
Note: Fusion MCP does not support dynamic procedure execution (BIP only runs SELECT data models). This tool is for discovery and understanding only.
package_name: required when the procedure lives inside a package.
Inputs: owner (required), object_name (required), package_name.
list_package_contentsB
List all public subprograms (procedures and functions) inside a Fusion Oracle package. Returns: procedure_name, overload index, object_type
Inputs: owner (required), package_name (required).
read_object_sourceA
Read the full source code of a stored object from ALL_SOURCE in Fusion.
object_type: PROCEDURE | FUNCTION | PACKAGE | PACKAGE BODY | TRIGGER | VIEW (omit to return all types for this name) Returns: {owner, name, source: {type: full_source_text}}
Inputs: owner (required), object_name (required), object_type.
search_columnsA
Find Fusion tables/views by column name or column comment. Example: search_columns('INVOICE_ID') to find every table with an invoice-id column.
Returns: owner, table_name, column_name, data_type, column_comment, table_comment
Inputs: keyword (required), limit.
search_objectsA
Search ALL_OBJECTS in Oracle Fusion / ERP Cloud by object name pattern.
keyword: substring to match against object_name (case-insensitive) object_types: optional filter, e.g. ['TABLE','VIEW','PROCEDURE','FUNCTION','PACKAGE'] owner: optional schema owner filter (e.g. 'FUSION') limit: max results (capped at 200)
Returns: owner, object_name, object_type, status, last_ddl_time, table_comment
Inputs: keyword (required), object_types, owner, limit.
search_sourceA
Full-text search across ALL_SOURCE in Fusion to find procedures/packages/functions that reference a keyword in their source code.
type_filter: PROCEDURE | FUNCTION | PACKAGE | PACKAGE BODY | TRIGGER Returns distinct owner/name/type — call read_object_source to get the full source.
Note: scans can be slow on large schemas; constrain type_filter and owner where possible.
Inputs: keyword (required), name_filter, type_filter, owner, +1 more.
search_tablesB
Find tables/views in Oracle Fusion whose name or comment contains the keyword.
Returns: owner, object_name, object_type, table_comment
Inputs: keyword (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: describe_table for table metadata, execute_query for read-only SQL, get_procedure_signature for argument details, list_package_contents for package subprograms, read_object_source for source code, and multiple search tools for different search scopes (columns, objects, source, tables). No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., describe_table, execute_query, search_columns). The verbs (describe, execute, get, list, read, search) are intuitive and match the action. No mixing of styles or ambiguous names.
With 9 tools, the server is well-scoped for its purpose of exploring and querying an Oracle Fusion database. Each tool earns its place without being overwhelming or too sparse.
The tool set covers most essential operations: discovery (search tools), description (describe_table), query execution (execute_query), and code examination (read_object_source, list_package_contents, get_procedure_signature). However, there is no simple 'list all tables' tool without a keyword, so users must search even for a broad listing. This minor gap prevents a perfect score.
Related MCP Connectors
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
MCP server for querying and analyzing data from ad platforms, analytics tools, and spreadsheets
Read-only MCP server for ClassQuill, a tutoring-business-management platform.
Cloud-hosted MCP server for secure AI access to enterprise data sources via CData Connect AI.