01 · Records and state owned
Granular agent tools over saved searches, tags, news and social mentions, analytics and media-intelligence assets; separate Mira MCP returns orchestrated AI-generated briefs and outcomes
Meltwater
Meltwater
Curated anchor platform in media intelligence and social listening with material relevance to the Marcom operating stack and a first-party developer surface.
Social, PR & communitySystem of engagementAgent-accessible 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
Granular agent tools over saved searches, tags, news and social mentions, analytics and media-intelligence assets; separate Mira MCP returns orchestrated AI-generated briefs and outcomes
03 · Actions and write paths
The targeted review confirmed this Meltwater capability surface: Granular agent tools over saved searches, tags, news and social mentions, analytics and media-intelligence assets; separate Mira MCP returns orchestrated AI-generated briefs and outcomes. It did not normalize every mutation tool. Treat writes as unapproved until each current tool, scope, plan and approval behavior is verified.
04 · Authentication and permissions
Access requires an API-customer MCP package and varies with subscribed products; API-token authentication is current, with OAuth documented as planned, so do not imply universal self-service access. Existing vendor identity, account, tenant, and permission controls should be treated as the authorization boundary.
05 · Monitoring, approval, and recovery
Require explicit human confirmation for costly, externally visible, destructive, or hard-to-reverse actions. Official Meltwater docs distinguish the composable data/tool server from the Mira assistant server. Access requires an API-customer MCP package and varies with subscribed products; API-token authentication is current, with OAuth documented as planned, so do not imply universal self-service access.
06 · Gaps and implementation limits
Official Meltwater docs distinguish the composable data/tool server from the Mira assistant server. Access requires an API-customer MCP package and varies with subscribed products; API-token authentication is current, with OAuth documented as planned, so do not imply universal self-service access.
First-party access
Documented surfaces
Agent access
MCP and adjacent posture
Verified first-party provider MCPMeltwater-hosted remote MCP plus separate Mira API MCPCurrent package-gated service
Role: provider
Read scope: Granular agent tools over saved searches, tags, news and social mentions, analytics and media-intelligence assets; separate Mira MCP returns orchestrated AI-generated briefs and outcomes
Write scope: Write scope was not separately normalized in this pass; inspect the official tool catalog before enabling actions.
Authentication: Access requires an API-customer MCP package and varies with subscribed products; API-token authentication is current, with OAuth documented as planned, so do not imply universal self-service access.
Approval boundary: Require explicit human confirmation for costly, externally visible, destructive, or hard-to-reverse actions.
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 access3
Event access1
Identity4
Governance4
Agent access4
UI extensibility3
Portability4
Observability3
Documentation4
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Meltwater ships these experiences.
Single-platform patterns
- Brand, media, and competitive-intelligence radar
- Social publishing command center
- Brand-signal briefing
- Response and escalation queue
Multi-platform compositions
- Meltwater + content-production platform: social publishing command center
- Meltwater + CRM or support system + analytics or work-management system: 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.
4 recorded sources
MCP / agent-role validationRepresentative source
https://developer.meltwater.com/guides/meltwater-mcp/overview ↗Official Meltwater docs distinguish the composable data/tool server from the Mira assistant server. Access requires an API-customer MCP package and varies with subscribed products; API-token authentication is current,…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
MCPSource inventory
https://developer.meltwater.com/docs/mcp ↗First-party MCP documentation or product announcement 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.
APISource inventory
https://developer.meltwater.com/ ↗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.
HomepageSource inventory
https://www.meltwater.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- May 27, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
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.