Permissions and availability
Loading server catalog…. Download catalog
Advarde MCPAvailable subject to your connection’s permissions.
Description: The full reference describes supported tools. Your connection may expose a smaller set.
Documentation: Getting started
Output: See the protocol description and workflow notes below.
Access: Workspace-scoped MCP authentication.
Read and write access
Read-only clients do not receive normal write, apply, or retry tools. Write access depends on token scopes, workspace membership, role, subscription, and account settings. Client disconnection is available for the credential currently in use. Tool-level checks remain authoritative.
Feature availability
Campaign optimizer and Automation rules require workspace feature enablement. Performance imports require platform enablement. Upstream features may require advertiser eligibility. Each affected tool lists its requirements.
Discover your access
Call tools/list using your actual connection to get its available tool names and schemas. The complete catalog on this page does not grant access or enable any feature.
Authentication
Use an MCP access token from MCP connections, or connect through OAuth. Send your token in the Authorization: Bearer header.
For full protocol initialization and tool discovery, use an MCP client. These examples show individual JSON-RPC requests.
Responses
200Successful protocol response
Inspect result.isError for tool-level failures, even when the HTTP status is 200.
202Notification accepted
MCP notifications return no JSON-RPC response body.
400Invalid request
Check the JSON-RPC envelope, parameters, and protocol version.
406Not acceptable
Accept must include application/json and text/event-stream.
429Rate limited
Wait for the Retry-After interval before making another request.
401Unauthorized
A valid, unexpired MCP bearer token is required.
403Access denied
Your connection needs access to this workspace and the requested operation.