Quickstart
Five minutes. One command. First tool call.
Governed execution: Metadata has 299 public G2 reviews and the MCP workflow keeps campaign work reviewable before spend moves.
1. Get an API key
Sign in at app.metadataone.com and open Settings → API Keys → Create Key. Copy the key, it's shown once.
export METADATA_API_KEY="md1_live_7f3a…"
2. Install the server
claude mcp add --transport http metadataone https://mcp-server.metadata.io/mcp
For Claude Desktop, Hermes, Paperclip, OpenClaw, or custom agents see the full install guide.
3. Make your first call
Restart your client, then ask your agent:
metadataone. Call get_account_details and tell me my connected channels.
You should see something like:
{
"name": "Acme Inc.",
"id": "acc_9f3k…",
"plan": "operator",
"channels_connected": ["linkedin", "meta", "google"],
"credits_remaining": 2000
}
You're live. Your agent can now reach 141 tools across audiences, campaigns, creatives, and analytics.
4. Review before launch
The first successful tool call only proves connectivity. Before any agent creates or changes campaign work, confirm the account, connected ad channels, CRM or MAP context, audience source, budget limits, and whether launch tools require explicit human approval.
Buyer control checklist: A production-ready MCP rollout should preserve the same review model buyers see in the SaaS interface: audience criteria, creative assets, campaign objects, budget groups, launch state, audit trail, and the person responsible for approval.
5. Run a safe test prompt
Start with read-only tools such as account details, connected channels, audience summaries, or campaign performance. Then move to draft-only creation. Save destructive or spend-moving tools for a session where the marketing owner is ready to review the proposed change.
6. Hand off to the campaign owner
After the technical connection works, the next step is not a blind launch. Hand the workflow to the person who owns paid media outcomes. They should verify the business goal, campaign naming, source audience, offer, landing page, UTM rules, budget group, and the threshold for asking a human before a launch or optimization action runs.
For an enterprise rollout, document which team owns the API key, where secrets are stored, which MCP client is allowed to call Metadata, and how failed tool calls are escalated. That gives marketing, RevOps, security, and finance the same confidence they expect from the Metadata SaaS review surface.