Help Center - IzeAds

IzeAds MCP server

MCP (Model Context Protocol) is an open standard that lets AI agents use external tools. The IzeAds MCP server exposes your account — metrics, campaigns, trackers, cloakers and creative library — as tools that any MCP-compatible agent can use. It is not tied to a single AI: Claude, Cursor, n8n, or your own agent all work the same way.

Endpoint and authentication

The server speaks Streamable HTTP (standard MCP). Authenticate with an IzeAds partner key in the Authorization header:

Endpoint: https://mcp.izeads.com/mcp
Header:   Authorization: Bearer izeads_live_xxxxxxxx

Generate the key in Integrations > Partner API. Without a valid key the server returns 401.

Works with any MCP client

Because it is standard MCP, any client that supports remote (HTTP) MCP servers connects the same way — just point it to the URL and provide the key. Examples: Claude (web, Code, Desktop), Cursor, n8n, and custom agents built with the MCP SDK (Python/TypeScript).

Self-describing tools

Every tool ships its own name, description and input schema. Your agent discovers all of them automatically via the standard tools/list call — no extra documentation needed to start using them.

Local (stdio) clients

If your client only supports local stdio MCP servers, use the mcp-remote bridge to reach the remote server:

npx mcp-remote https://mcp.izeads.com/mcp \
  --header "Authorization: Bearer izeads_live_xxxxxxxx"

Scopes

What an agent can actually do is limited by the key scopes. Create a full-access key or a restricted one (for example, metrics read-only) depending on the use case. This is how you safely give an agent access to only part of the account.

Prefer plain REST?

The MCP server is a wrapper over the same partner API. If you are building a custom integration and do not need MCP, you can call the REST API at https://api.izeads.com/api/partner/v1 directly with the same Bearer key.