01 · Records and state owned
Accounts, workspaces, apps, audiences, data plans and versions, data points and events, feeds, calculated attributes, transformations, services, users, warehouse syncs, and DSRs.
mParticle
mParticle
Curated major addition platform in customer data platform with material relevance to the Marcom operating stack and a first-party developer surface.
Marketing automation, lifecycle & CDPSystem of engagementExtensible SaaSReverse ETL / activation
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.
02 · Data you can retrieve
Retrieve and manage platform configuration, data plans, audiences, feeds, transformations, users, and supported profile/event context.
03 · Actions and write paths
Create and update platform entities; ingest events and attributes; configure feeds and warehouse sync; submit and manage data-subject requests.
04 · Authentication and permissions
mParticle API credentials, workspace/app access, service-specific credentials, region, and data-plan governance apply.
05 · Monitoring, approval, and recovery
Protect identity resolution, consent, retention, data-plan approval, destination routing, DSR handling, and warehouse synchronization lineage.
06 · Gaps and implementation limits
Only an unofficial community MCP was found. Official APIs are broad but split across services with distinct authentication, quotas, and product availability.
First-party access
Documented surfaces
Warehouse Sync SQL models ↗mParticle Warehouse Sync defines warehouse data models for one-time, on-demand, or recurring pulls from supported warehouses. SQL executes against the connected customer warehouse, subject to connection and pipeline permissions.Source: Warehouse Sync User GuidemParticle Warehouse Sync Reverse ETL ↗mParticle explicitly describes Warehouse Sync as its Reverse ETL solution for ingesting warehouse profile or event data into mParticle. Forwarding onward uses separate output integrations, and input-protection mode governs profile changes.Source: Warehouse Sync API OverviewAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceProduct ↗Native platform experience
Agent access
MCP and adjacent posture
Third-party/community MCP only; no first-party provider verifiedCommunity MCP only; first-party status unresolvedNo first-party provider verified
Role: third_party_only
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: Not applicable to a first-party MCP provider.
Approval boundary: Any customer-built adapter must define its own approval and confirmation controls.
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 access1
UI extensibility4
Portability3
Observability3
Documentation4
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that mParticle ships these experiences.
Single-platform patterns
- Customer-data quality and audience routing console
- Lifecycle journey debugger
- Audience activation workbench
- Campaign QA and approval room
Multi-platform compositions
- mParticle + CRM or commerce system: lifecycle journey debugger
- mParticle + warehouse or CDP + content-production platform: cross-system decision workspace
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.
6 recorded sources
Platform core validationRepresentative source
https://docs.mparticle.com/developers/apis/platform/overview/ ↗Accounts, workspaces, apps, audiences, data plans and versions, data points and events, feeds, calculated attributes, transformations, services, users, warehouse syncs, and DSRs. Create and update platform entities;…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party core-access review
APISource inventory
https://docs.mparticle.com/developers/apis/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://docs.mparticle.com/developers/ ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://www.mparticle.com/ ↗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.
Warehouse Sync SQL modelsTargeted review
Warehouse Sync User Guide ↗mParticle Warehouse Sync defines warehouse data models for one-time, on-demand, or recurring pulls from supported warehouses. SQL executes against the connected customer warehouse, subject to connection and pipeline…
- Publisher updated
- Jun 22, 2026
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party access review
mParticle Warehouse Sync Reverse ETLTargeted review
Warehouse Sync API Overview ↗mParticle explicitly describes Warehouse Sync as its Reverse ETL solution for ingesting warehouse profile or event data into mParticle. Forwarding onward uses separate output integrations, and input-protection mode…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party access review
Verified fact
Tied to the representative first-party source or targeted access review.
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.