01 · Records and state owned
Campaigns, budget groups, audiences, target groups, ads, brand assets, offers, keywords, experiments, account insights, segments, integrations, and ABM or intent resources.
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
Search campaigns, audiences, ads, experiments, budgets, integrations, account journeys, funnel metrics, keywords, segments, and target criteria through 44 read-only tools.
03 · Actions and write paths
Create or launch campaigns, change budgets, build audiences and target groups, generate or edit creative, manage channel connections, and modify offers, segments, or keywords.
04 · Authentication and permissions
The hosted server uses a Metadata account access token and interactive account authorization; tools also respect user permissions and account-level controls, with OAuth used for connected systems.
05 · Monitoring, approval, and recovery
Metadata labels 31 tools destructive because they create, update, delete, connect, or spend. Its guidance recommends read-only validation and budget review before launch during implementation.
06 · Limits and caveats
Tools register dynamically from Metadata.io and Make.com integrations, so each account's catalog depends on connected systems; the published connection walkthrough currently requires Claude Pro for setup.
Agent access
MCP support
Official MCP serverMetadata-hosted remote MCPCurrent documented service
Support: Official MCP server
Read scope: Use 44 read-only tools to inspect campaigns, budget groups, audiences, ads, experiments, integrations, funnel performance, account journeys, segments, and targeting criteria.
Write scope: Use 31 destructive tools to create, update, connect, disconnect, launch, pause, or allocate spend across campaigns, audiences, creative, budgets, offers, keywords, and segments.
Authentication: Connect to Metadata's hosted endpoint with an account-generated access token, then complete Metadata login and app authorization for the session; downstream channel or CRM connections use OAuth.
Approval boundary: Require named approval before campaign launch, pause or restart, daily-budget changes, channel disconnection, or other destructive tools that can alter delivery, access, or live spend.
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 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 Metadata.io ships them.
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 ↗Tool categories, dynamic registration, read-only versus destructive classification, user permissions, account controls, and budget guidance
- Publisher updated
- Apr 10, 2026
- BYO-UI reviewed
- Jul 22, 2026
Metadata MCP tool classes and safety guidance reviewed 2026-07-22
Developer docsSource inventory
https://help.metadata.io/portal/articles?category=Integrations ↗First-party developer documentation.
- 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.
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.
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 ↗Hosted server URL, account token generation, Metadata login, app authorization, Claude requirement, and account verification
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
Metadata MCP connection and account authorization reviewed 2026-07-22
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.
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.