Skip to main content
Glama
ruya-grp

fusion-query-mcp

by ruya-grp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to fusion-query-mcp

No user-submitted related servers found.

    Related Servers

    • Fusion Schema MCP Server

      marat-ak
      F
      license
      Not graded
      quality
      B
      maintenance
      Grounds a Fusion-SQL agent against Oracle Fusion schema catalog, enabling table/column search, validation, and relationship discovery.
      -

    • Oracle MCP

      danangpriabada
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with secure, structured access to Oracle Database through MCP, enabling SQL execution, metadata exploration, and stored procedure execution.
      -

    • Oracle Fusion HCM MCP

      klemrabet
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Oracle Fusion HCM via REST, SOAP, SQL, and BPM, supporting catalog search, operation execution, ESS processes, BI Publisher reports, security diagnostics, and workflow management.
      -

    • mcp-oraclefusion

      elabbarw
      A
      license
      B
      quality
      D
      maintenance
      Read-only access to Oracle Fusion Cloud ERP data via natural language queries, with support for accounts payable, procurement, general ledger, and more.
      30
      3
      MIT

    • Oracle DB MCP Server

      titan213
      A
      license
      A
      quality
      C
      maintenance
      Enables AI tools to interact with Oracle databases through query execution, schema browsing, stored procedure calls, and transaction management. Supports multiple database connections with safety features like read-only mode and dangerous query detection.
      16
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 40 tools

    Disambiguation4/5

    Most tools have crisp distinct purposes, and the domain prefixes (docs_, api_, soap_) in names do real disambiguation work. However, there are several deliberate parallel pairs — live vs docs-snapshot describe/search, run_query vs adhoc_query vs run_report, validate_report vs validate_query — whose boundaries are only clear after reading the lengthy descriptions, so a skimming agent could easily pick the wrong query or validation path.

    Naming Consistency4/5

    The set overwhelmingly follows fusion_<verb>_<noun> (or fusion_<module>_<verb>_<noun> for docs_/api_/soap_), which is a strong, predictable convention across 40 tools. A few outliers break the verb-first shape — fusion_health_check, fusion_adhoc_query, fusion_bootstrap — but they remain readable and do not undermine the overall pattern.

    Tool Count3/5

    40 tools is heavy and exceeds the comfortable band, though the count reflects a genuinely broad scope: SQL, BI reports, REST, SOAP, ESS/FBDI, approvals, pods, and docs each form their own cluster. The live-vs-docs-snapshot duplications and the three overlapping query execution paths inflate the number without adding new capability, making the surface larger than it needs to be.

    Completeness4/5

    The surface covers the full lifecycle across channels: schema exploration, query execution (report, ad-hoc, free-SQL), validation with fixtures, guarded write actions (REST, SOAP, ESS, FBDI), monitoring (job status/log, health check), and repair (bootstrap, interface-data correction). Minor gaps exist — no fixture deletion, no report deletion, no direct REST record GET by ID, no job cancellation — but all are workable around or explained as inherent constraints.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources