01 · Records and state owned
Campaigns, templates, catalogs, exports, events, experiments, journeys, lists, users, reporting, and other configured Iterable resources.
Iterable
Iterable
Iterable is included for an official local MCP server that can inspect lifecycle data in safe read-only mode and, through separate per-key gates, expose PII, resource writes, campaign controls, and cross-channel sends.
Marketing automation, lifecycle & CDPSystem of engagementExtensible SaaS
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
Inspect campaigns, templates, catalogs, exports, events, experiments, journeys, lists, and reporting. User profile data is excluded unless the key's separate PII gate is enabled.
03 · Actions and write paths
When separately enabled, create, update, archive, or delete resources; schedule, trigger, or abort campaigns and journeys; track events; and send email, SMS, push, in-app, or WhatsApp messages.
04 · Authentication and permissions
One active Iterable API key and its US, EU, or custom endpoint identify the project. API-key scope and three saved per-key gates - PII, writes, and sends - determine the exposed tools; sends also require writes.
05 · Monitoring, approval, and recovery
Keep PII, writes, and sends disabled for production keys unless required. Use separate sandbox and production keys, show the active key and endpoint, and require review before profile access, deletion, campaign scheduling or abort, journey triggers, event tracking, or sends.
06 · Limits and caveats
The server is Beta, runs locally on Node.js 20 or later, and stores one active key selection locally. Some clients cap a server at 100 tools, so enabling every elevated gate can prevent the full catalog from loading.
Agent access
MCP support
Official MCP serverIterable official open-source local MCPBeta open-source local server; v1.8.1 released July 9, 2026
Support: Official MCP server
Read scope: Read campaigns, templates, catalogs, exports, events, experiments, journeys, lists, and reporting; user profiles require the separate PII gate.
Write scope: Optional advanced modes can create, update, archive, delete, schedule, trigger, abort, and send through the underlying Iterable APIs.
Authentication: Iterable API key
Approval boundary: Retain the safe defaults in production. Require explicit approval for sends, campaign activation, destructive actions, and PII access.
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 access4
Identity4
Governance4
Agent access4
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 Iterable ships them.
Single-platform patterns
- Cross-channel journey and messaging cockpit
- Lifecycle journey debugger
- Audience activation workbench
- Campaign QA and approval room
Multi-platform compositions
- Iterable + CRM or commerce system: lifecycle journey debugger
- Iterable + 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.
5 recorded sources
MCP / agent-role validationRepresentative source
https://github.com/Iterable/mcp-server ↗Iterable publishes an official local server whose setup defaults to no PII, no writes, and no sends; advanced flags can enable broad API-backed actions.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://api.iterable.com/api/docs ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Developer docsSource inventory
https://support.iterable.com/hc/en-us/categories/360002695831-API-Documentation ↗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://iterable.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Jun 4, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://support.iterable.com/hc/en-us/articles/205480365-Webhooks-Overview ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- 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.