01 · Records and state owned
Visitor profile attributes, badges, and audience memberships returned from a configured Moments API engine using an anonymous ID or a visitor ID attribute.
Tealium
Tealium AudienceStream
Tealium AudienceStream belongs in Atlas because its managed Moments API MCP retrieves tightly selected visitor attributes, badges, and audiences for real-time personalization without platform mutation tools.
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
Retrieve selected visitor context through two tools: lookup by Tealium anonymous ID or by a configured visitor ID attribute and value.
03 · Actions and write paths
No AudienceStream mutation tool is documented. Both published tools retrieve visitor context from a configured Moments API engine for downstream use.
04 · Authentication and permissions
Access requires an active Moments API engine and support-issued feature API key sent in X-Tealium-Api-Key; calls also require account, profile, engine, Origin, and Referer parameters.
05 · Monitoring, approval, and recovery
Tealium recommends a separate engine per MCP use case containing only necessary attributes, badges, and audiences, which narrows exposure and simplifies auditing and maintenance over time.
06 · Limits and caveats
The endpoint region must match the Moments API engine. Attribute names are required for useful LLM context because default numeric IDs are not meaningfully interpretable.
Agent access
MCP support
Official MCP serverTealium Moments API managed MCPCurrent documented service
Support: Official MCP server
Read scope: Use anonymous-ID or visitor-ID-attribute lookups to retrieve the attributes, badges, and audience memberships explicitly configured in one Moments API engine.
Write scope: The managed server publishes two retrieval tools and no profile, audience, connector, rule, or engine mutation action; downstream personalization occurs outside this MCP.
Authentication: Connect over regional streamable HTTP using a Tealium Support-issued feature key in X-Tealium-Api-Key, plus required Origin and Referer headers and engine-scoping parameters on every request.
Approval boundary: The MCP itself is read-only; approval belongs at engine configuration and at any downstream personalization or automation that acts on the retrieved visitor context before production use.
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 Tealium ships them.
Single-platform patterns
- Consent-aware audience and activation cockpit
- Lifecycle journey debugger
- Audience activation workbench
- Campaign QA and approval room
Multi-platform compositions
- Tealium AudienceStream + CRM or commerce system: lifecycle journey debugger
- Tealium AudienceStream + 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://docs.tealium.com/server-side/moments-api/managed-mcp-server/ ↗Two visitor lookup tools, streamable HTTP deployment, feature API key, required scope parameters, regional endpoint, and dedicated-engine guidance
- Publisher updated
- Oct 24, 2025
- BYO-UI reviewed
- Jul 22, 2026
Tealium Moments API MCP tools, authentication, and minimization guidance reviewed 2026-07-22
APISource inventory
https://docs.tealium.com/server-side/ ↗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://docs.tealium.com/ ↗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://tealium.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Jun 25, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://docs.tealium.com/server-side/connectors/ ↗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.