01 · Records and state owned
Saved searches, tags, news and social mentions, analytics, insights, and media-intelligence assets; Mira separately returns completed answers, briefs, and reports.
Meltwater
Meltwater
Meltwater belongs in Atlas because its hosted MCP exposes saved-search media intelligence as granular tools, while a separate Mira server returns Meltwater-orchestrated briefs and reports.
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
Find configured searches and tags, retrieve news or social mentions, and analyze Meltwater data; use Mira when a completed brief, answer, or report is required.
03 · Actions and write paths
The reviewed overview identifies retrieval and analysis tools but no state-changing operation; verify the runtime catalog before enabling any mutation.
04 · Authentication and permissions
Current access requires an API-customer MCP subscription and API token; product entitlements determine available tools, while OAuth 2.0 is documented as planned for later in 2026.
05 · Monitoring, approval, and recovery
The granular server lets the client agent orchestrate tools; Mira performs Meltwater-side orchestration. Keep those execution models visible so generated outcomes are not mistaken for raw evidence.
06 · Limits and caveats
Tool availability varies by subscribed Meltwater products and package. The server exposes its current catalog dynamically, and public documentation does not provide a fixed tool list.
First-party access
Documented surfaces
Agent access
MCP support
Official MCP serverMeltwater-hosted remote MCP plus separate Mira API MCPCurrent package-gated service
Support: Official MCP server
Read scope: Retrieve configured searches, tags, media mentions, analytics, and insights through granular tools, or request a Meltwater-orchestrated answer, brief, or report through Mira.
Write scope: No state-changing operation is stated in the reviewed overview; inspect the connected server's current tools before authorizing any mutation there.
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: No mutation is verified from the overview; require tool-level review before approving any newly exposed action that changes Meltwater configuration or downstream outputs at runtime.
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 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 Meltwater ships them.
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.
3 recorded sources
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.
Developer docsSource inventory
https://developer.meltwater.com/guides/meltwater-mcp/overview ↗The recorded supporting URL returned HTTP 404.
- 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.
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 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.