Metadata MCP Connector MCP server

Metadata MCP Connector

Connect your Metadata account to an MCP-compatible assistant to review B2B advertising performance, plan audiences, prepare brand-aware ad concepts, and check campaign launch readiness.

This repository contains client configuration, four workflow skills, and an optional local MCP adapter for Metadata's hosted service. It does not contain or self-host the production server implementation. The connector and skills are free to install; an existing Metadata account with MCP access is required. Metadata subscriptions, generation allowances, channel permissions, and service terms apply separately.

Production endpoint

• URL: https://mcp-server.metadata.io/mcp
• Transport: Streamable HTTP over HTTPS
• Authentication: browser-based OAuth in compatible clients; personal access token in Gemini CLI and the local MCP bundle
• Privacy: https://metadata.io/privacy-policy
• Support: https://help.metadata.io

No passwords, API keys, fixed account identifiers, installation scripts, or background jobs are included.

Workflows and sample prompts

Cursor

This package uses .cursor-plugin/plugin.json, root mcp.json, and the standard skills/ layout. Install it through Cursor's plugin controls when available in the Marketplace, then connect Metadata through OAuth. Marketplace submission is separate from approval.

For an immediate MCP-only connection, add this to your Cursor MCP configuration:

{"mcpServers":{"metadata":{"url":"https://mcp-server.metadata.io/mcp"}}}

Complete browser authentication, confirm the account identity, and start with a read-only request. The MCP-only configuration does not install the bundled skills.

Gemini CLI

gemini extensions install https://github.com/f-o-x11/metadata-mcp-connector

During installation, enter your own Metadata MCP personal access token in the sensitive extension setting. Obtain the token through your Metadata account or administrator. Enter the raw token without a Bearer prefix. Gemini stores this sensitive setting in the system keychain; never paste it into chat or commit it to a repository.

Restart Gemini CLI after installation and inspect the connection with /mcp. Gemini reads the root gemini-extension.json, loads the four bundled skills, and connects using httpUrl for Streamable HTTP. No command or local server process is required. Start with an account-identity check before reading other data.

To change the token, run gemini extensions config metadata-mcp-connector. An explicitly supplied METADATAMCPTOKEN environment variable can also provide the token for a controlled CLI session.

The Gemini package uses Metadata's supported token authentication because Gemini CLI 0.60.0 rejects the current OAuth callback when its required issuer parameter is absent. It does not disable OAuth security checks. Other clients retain their normal OAuth configuration.

Smithery and local MCP bundles

Shortened. The full README is on GitHub.