01 · Records and state owned
More than 75 tools across 16 categories covering marketing analytics, campaign management, audiences, account lists, budgets, creative generation, integrations, intent and performance operations
Metadata.io
Metadata
A strategically important B2B demand platform whose official MCP exposes a broad operational surface across campaigns, audiences, analytics, creative, budgets, and connected systems.
Marketing automation, lifecycle & CDPSystem of engagementBYO-UI-ready platform
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
More than 75 tools across 16 categories covering marketing analytics, campaign management, audiences, account lists, budgets, creative generation, integrations, intent and performance operations
03 · Actions and write paths
Metadata's first-party MCP/agent surface includes state-changing tools in the documented capability area: More than 75 tools across 16 categories covering marketing analytics, campaign management, audiences, account lists, budgets, creative generation, integrations, intent and performance operations. The audit did not enumerate every mutation; verify the current tool catalog and require explicit confirmation for consequential actions.
04 · Authentication and permissions
Authentication model is documented by the vendor; inspect the cited source before implementation. Official Metadata documentation confirms a hosted endpoint and account authorization. The public tool reference is unusually detailed, but consequential campaign, budget and activation operations still need approval controls and plan/permission verification.
05 · Monitoring, approval, and recovery
Official Metadata documentation confirms a hosted endpoint and account authorization. The public tool reference is unusually detailed, but consequential campaign, budget and activation operations still need approval controls and plan/permission verification. Official Metadata documentation confirms a hosted endpoint and account authorization. The public tool reference is unusually detailed, but consequential campaign, budget and activation operations still need approval controls and plan/permission verification.
06 · Gaps and implementation limits
Official Metadata documentation confirms a hosted endpoint and account authorization. The public tool reference is unusually detailed, but consequential campaign, budget and activation operations still need approval controls and plan/permission verification.
Agent access
MCP and adjacent posture
Verified first-party provider MCPMetadata-hosted remote MCPCurrent documented service
Role: provider
Read scope: More than 75 tools across 16 categories covering marketing analytics, campaign management, audiences, account lists, budgets, creative generation, integrations, intent and performance operations
Write scope: State-changing tools are present in the documented scope; review the official tool catalog and require confirmation for consequential actions.
Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.
Approval boundary: Official Metadata documentation confirms a hosted endpoint and account authorization. The public tool reference is unusually detailed, but consequential campaign, budget and activation operations still need approval controls and plan/permission verification.
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 extensibility3
Portability4
Observability3
Documentation5
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Metadata.io ships these experiences.
Single-platform patterns
- Demand engine operator cockpit
- Campaign exception and budget workbench
- Account and audience activation room
Multi-platform compositions
- Metadata + CRM + revenue intelligence: account-prioritized campaign workspace
- Metadata + creative generation + work management: governed campaign launch room
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
MCP toolsRepresentative source
https://help.metadata.io/portal/articles/metadata-mcp-supported-tools ↗Official Metadata documentation confirms a hosted endpoint and account authorization. The public tool reference is unusually detailed, but consequential campaign, budget and activation operations still need approval…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
HomepageSource inventory
https://metadata.io/ ↗Product positioning and platform overview.
- Publisher updated
- Jun 12, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
MCP connectionSource inventory
https://help.metadata.io/portal/articles/metadata-mcp-how-to-connect ↗First-party connection and authentication guidance.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
MCP overviewSource inventory
https://metadata.io/one/ ↗First-party explanation of MetadataONE and MCP-enabled operation.
- Publisher updated
- Feb 25, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Help centerSource inventory
https://help.metadata.io/portal ↗First-party operational and integration 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.
Developer docsSource inventory
https://help.metadata.io/portal/categories/integrations ↗First-party developer 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 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.