Metadata MCP Server (MetadataONE)
The MetadataONE Model Context Protocol server — Metadata's only public developer surface. 141 documented tools let an MCP client (Claude Code, Claude Desktop, Hermes, Paperclip, OpenClaw or a custom agent) run B2B paid media end to end: build firmographic, technographic, Bombora-intent, G2-intent, native-criteria, retargeting and CSV-uploaded audiences; extract brand kits and generate on-brand image, video, carousel, document and conversation ads; create lead-gen and landing-page offers; assemble Precision (1x1x1) or Channel-First (NxNxN) campaigns inside a budget group; launch them to real spend on LinkedIn, Meta, Google, Microsoft and Reddit; manage keywords and Google/Microsoft ad extensions; and read funnel, experiment, ABM and pipeline analytics. Authentication is a bearer API key (md1_live_ prefix) scoped to a single account, with seven product permission scopes that separate read, draft and launch. The endpoint also serves RFC 8414 authorization-server and RFC 9728 protected-resource metadata anonymously, so an OAuth-capable client can discover it without credentials. Campaigns are created in Draft and only launch_campaign moves real budget.