Oracle

Oracle CX

Oracle CX is included for its broad Fusion Sales and Service REST surface and for Oracle Integration's project-scoped MCP bridge, which can publish selected CX integrations as agent tools without constituting a fixed Oracle CX-native server.

CRM, revenue & customerSystem of recordExtensible SaaS
Representative source ↗Product site ↗Suggest a correction
An illustration of access surfaces surrounding a governed system.
System roleSystem of record
Access maturityExtensible SaaS
MCP supportBridge
Reference updatedApr 16, 2026
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Accounts, contacts, leads, opportunities, activities, service requests, assets, products, notes, teams, territories, and related sales/service records.

02 · Data you can retrieve

View and query authorized Oracle Fusion Sales and Service resources, including nested opportunity, account, lead, activity, and asset data.

03 · Actions and write paths

Create, update, and delete supported CRM and service resources through documented REST methods, including leads, opportunity relations, notes, and activities.

04 · Authentication and permissions

Direct CX REST calls use Oracle Fusion application authentication and data-security privileges. The MCP bridge instead authenticates a confidential Oracle Integration client through OAuth client credentials with Integration scopes and at least the ServiceInvoker role; downstream CX permissions depend on the registered integration connection.

05 · Monitoring, approval, and recovery

Expose only integrations explicitly registered as agentic AI tools within an MCP-enabled Oracle Integration project. Track the confidential client and ServiceInvoker grant separately from the CX connection identity, and make any consequential-operation approval an explicit part of the registered integration design.

06 · Limits and caveats

No fixed Oracle CX-native MCP catalog was verified. Oracle Integration exposes only registered tools per enabled project, uses a service application rather than per-user MCP authorization, and inherits each integration's downstream CX scope, side effects, release compatibility, and consumption.

First-party access

Documented surfaces

MCP / agent surface ↗Verified Oracle Integration MCP provider bridge; no fixed Oracle CX-native provider catalog verifiedAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceProduct ↗Native platform experience

Agent access

MCP support

BridgeOracle Integration-hosted project MCP bridge to selected Oracle CX integrationsCurrent documented Oracle Integration MCP service; no Oracle CX-native catalog verified

Support: Bridge

Read scope: Tool-specific reads are available when an Oracle Integration project publishes a registered CX integration; the native CX REST catalog remains the authoritative resource surface. No standard MCP read catalog applies to every Oracle CX deployment.

Write scope: A published integration can perform CX writes supported by its configured REST or adapter workflow, but MCP itself supplies no uniform mutation set. Effects and reversibility must be determined from each registered integration.

Authentication: OAuth client credentials for an Oracle Integration confidential application, yielding a bearer access token for the project MCP URL; the application requires Integration scopes and ServiceInvoker.

Approval boundary: Oracle Integration registration controls which automations are callable, but the reviewed MCP pages do not promise per-call human confirmation. BYO-UI should surface the project, integration, service identity, downstream CX operation, and any embedded human-in-the-loop step before executing a mutation.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access1
Identity4
Governance4
Agent access2
UI extensibility4
Portability3
Observability3
Documentation4

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Oracle ships them.

Single-platform patterns

  • Enterprise customer and opportunity workspace
  • Account journey room
  • Pipeline-quality debugger
  • Customer expansion cockpit
Use in the brief builder →

Multi-platform compositions

  • Oracle CX + marketing or intent platform: account journey room
  • Oracle CX + conversation or support system + analytics or warehouse: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

7 recorded sources
Developer docsSource inventory
https://docs.oracle.com/en/cloud/saas/ ↗

First-party developer documentation or platform overview.

Publisher updated
Jul 7, 2026
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://www.oracle.com/cx/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
Jun 5, 2025
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

MCP / agent-role validationTargeted review
https://blogs.oracle.com/integration/wp-content/uploads/sites/109/2025/12/Getting-Started-with-Agentic-AI-Using-Oracle-Integration-SHO2796.pdf ↗

Oracle Integration can expose integrations involving Oracle CX as MCP tools, but no product-native Oracle CX provider MCP was verified.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Targeted first-party MCP/agent-role claim review; exact live reachability was not independently retested for every URL.

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.