Fusion BIP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FUSION_MCP_ENABLE_DELETE | No | Set to 1 to enable the destructive delete_catalog_object tool. Off by default. | 0 |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_fusionA | Run a read-only SELECT against Oracle Fusion and return the rows as XML. Args: sql: A single SELECT statement. No trailing semicolon. Add WHERE/ROWNUM to keep the result small — BIP serializes the whole set. columns: Output column aliases in SELECT order, upper-case identifiers. Alias every column in the SQL to a simple upper-case name. fusion_user: Fusion user to run as (default bip_user). |
| run_reportA | Run a deployed BIP report and return its output. Args: report_path: Full catalog path, e.g. /Custom/MyReports/MY_RPT.xdo fusion_user: Fusion user to run as (default bip_user). |
| get_catalog_objectA | Download a catalog object definition (.xdm or .xdo) for inspection. Args: object_path: Full catalog path, e.g. /Custom/MyReports/MY_DM.xdm fusion_user: Fusion user to run as (default bip_user). |
| deploy_data_modelA | Deploy a BIP data model (.xdm) to a catalog folder. WRITE operation. Args: name: Data model name (letters, digits, underscore). xdm_xml: Complete data model XML. Use ApplicationDB_FSCM as data source. folder: Target folder, e.g. /Custom/MyReports or /~bip_user. replace: Delete any existing model of the same name first (default true). fusion_user: Must have the BIP Author role (default bip_user). |
| deploy_reportA | Deploy a BIP report (.xdo) linked to a data model. WRITE operation. Args: name: Report name (letters, digits, underscore). dm_path: Path to the linked data model, e.g. /Custom/MyReports/MY_DM.xdm folder: Target folder for the report. replace: Delete any existing report of the same name first (default true). fusion_user: Must have the BIP Author role (default bip_user). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct operation: direct SQL query, report execution, catalog object download, data model deployment, and report deployment. There is no overlap or ambiguity between them.
All five tool names follow a consistent verb_noun pattern in snake_case (query_fusion, run_report, get_catalog_object, deploy_data_model, deploy_report). Minor variation in the verb (query, run, get, deploy) is natural and predictable.
With only 5 tools, the server is tightly scoped to core Fusion BIP operations: querying data, running reports, and managing catalog objects. Each tool earns its place, and the count is ideal for the stated purpose.
The tool set covers the main lifecycle: query, run, get, deploy (with replace for updates). However, it lacks a catalog listing/browsing tool and an explicit delete operation, which would make it fully self-sufficient. These are workable gaps for agents that already know the exact catalog paths.