Oracle

Oracle Responsys

Oracle Responsys belongs in Atlas for profile, campaign, content, and cross-channel messaging APIs; agent access is available through configured Oracle Integration workflows, not a native Responsys MCP.

Marketing automation, lifecycle & CDPSystem of engagementExtensible SaaS
Representative source ↗Product site ↗Suggest a correction
An illustration of access surfaces surrounding a governed system.
System roleSystem of engagement
Access maturityExtensible SaaS
MCP supportBridge
Reference updatedMar 3, 2023
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

Profile lists and recipients, profile extensions, supplemental tables, filters, campaigns and schedules, programs, events, content-library folders/documents/media, and organizational access.

02 · Data you can retrieve

Retrieve profiles, list extensions, supplemental data, campaign schedules, filters, folders, content, and reporting-related resources.

03 · Actions and write paths

Create/update profile data and content-library objects; trigger or merge-trigger email, SMS, and push campaigns; manage schedules and selected organizational mappings.

04 · Authentication and permissions

Responsys API users authenticate to an account-specific endpoint and receive a token plus service endpoint; functional roles and Organizational Access Control govern all subsequent requests.

05 · Monitoring, approval, and recovery

Consent, suppression, profile identity, organizational access, preview/testing, content approval, and send authorization must remain explicit.

06 · Limits and caveats

Oracle Integration can publish configured automation components as MCP tools and connect them through the Responsys Adapter; this does not expose Responsys' entire REST API automatically.

First-party access

Documented surfaces

MCP / agent surface ↗Verified first-party Oracle Integration bridge; no Responsys-native MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceProduct ↗Native platform experience

Agent access

MCP support

BridgeOracle Integration MCP server exposing configured Responsys Adapter workflows; no native Responsys providerCurrent Oracle Integration bridge; no product-native Responsys provider verified

Support: Bridge

Read scope: No native Responsys MCP read catalog exists. Oracle Integration can expose selected adapter-backed retrieval workflows as tools, with data and objects determined by each integration.

Write scope: No native Responsys MCP write catalog exists. Configured Oracle Integration tools can invoke selected adapter workflows, with mutations and send behavior defined by each integration.

Authentication: The bridge combines Oracle Integration MCP access with configured Responsys Adapter credentials; direct Responsys API users authenticate to an account endpoint and receive a time-limited token plus service endpoint.

Approval boundary: Treat every bridge tool as a purpose-built integration: review its inputs, recipient scope, content, channel, and launch effect before exposing any profile mutation, event trigger, or send action.

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 email, mobile, and lifecycle operations room
  • Lifecycle journey debugger
  • Audience activation workbench
  • Campaign QA and approval room
Use in the brief builder →

Multi-platform compositions

  • Oracle Responsys + CRM or commerce system: lifecycle journey debugger
  • Oracle Responsys + warehouse or CDP + content-production platform: 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
HomepageSource inventory
https://www.oracle.com/cx/marketing/campaign-management/ ↗

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

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

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

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.