Fusion BIP MCP Server
Related Servers
Alternatives to Fusion BIP MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceA local stdio MCP server providing read-only access to Oracle Fusion/ERP Cloud databases via the BI Publisher SOAP API, enabling object discovery, table descriptions, source reading, and SELECT queries.9-
- AlicenseAqualityBmaintenanceAn MCP server that lets AI models interact with Oracle Fusion Cloud HCM across its entire REST surface. It uses generic, schema-aware tools to dynamically discover licensed modules and resources without per-endpoint code.6Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to explore Oracle Fusion Cloud schema metadata, run pre-built BI Publisher reports with bind parameters, and validate results against trusted ground truth.40Apache 2.0
- AlicenseAqualityAmaintenanceMCP server that exposes ERP functionalities to AI agents, enabling read-only queries for sales orders and inventory, and human-in-the-loop purchase requisition creation and approval.59MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that connects Claude Desktop to an Oracle Fusion Cloud instance. It exposes suppliers, purchase orders, invoices, and project costs as callable tools.-
- FlicenseNot gradedqualityBmaintenanceMCP server enabling AI agents to directly query and manage Power BI datasets, reports, and workspaces via DAX, with built-in data security policies and support for both Power BI Desktop and Service.1-
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.