AdsViewer MCP Server

01 What it is

The Model Context Protocol (MCP) is an open standard that lets AI assistants, such as Claude, call tools in other products. The AdsViewer MCP server lets an assistant you choose answer questions about your advertising performance using your organization's data in AdsViewer. It also lets the assistant draft changes for you to review.

The assistant always acts as you. It can only reach organizations you are an active member of, and it stops working when you are no longer an active member of any organization. Within an organization, your role limits it only for automations (see section 03).

02 Connecting and authentication

• No API keys. You connect by signing in to AdsViewer in your browser (OAuth 2.0 with PKCE). Your AdsViewer password and your ad-platform credentials are never shared with the AI assistant.
• Explicit consent. When a hosted assistant asks to connect, AdsViewer shows a consent screen showing where access is being sent and the organization the connection starts in. The connection covers every organization you are an active member of. Nothing is connected until you approve. Callbacks to the assistant are restricted to an allowlist of known destinations.
• Expiring, revocable credentials. Access tokens expire after 90 days. We store only a one-way hash of each token, and every request is checked against it, so a revoked token stops working within about a minute.
• Encrypted in transit. All traffic to the MCP server uses HTTPS (TLS).

03 What the assistant can access

Every request is checked against your active organization memberships at the time it is made. The assistant can work in any organization you belong to, and nowhere else. If you are removed from an organization, the assistant loses access to it within about a minute. Drafting automations needs the same permission over MCP as in AdsViewer. Other role restrictions are not yet applied over MCP, so any active member can read the data listed below.

Within that scope, the assistant's capabilities fall into four levels:

Read — no approval needed

• Performance data and reporting for the ad accounts, campaigns, ads, and products connected to your organization.
• Your saved configuration, such as reports, alerts, custom metrics, and dimensions, so the assistant can explain and build on it.
• Organization context: organization details (including plan and billing contact), connected platforms, and members' names, email addresses, and roles.

Propose — always requires your approval

• The assistant can draft new or updated reports, alerts, metrics, and automations. A draft is only a proposal: nothing is saved or changed through MCP. To apply it, you make the change yourself inside AdsViewer, for example from the Agent Hub.
• Once saved in AdsViewer, automations that change ads, budgets, or your product catalog keep their own human-review step, unless an authorized user turns on automatic approval for that automation. The exception is stock-availability changes, which are approved automatically unless review is turned on for that automation.

Create — limited, non-destructive

• On request, the assistant can generate draft images and short videos for creative exploration. The assistant receives a link to each result. They are never published, and usage is capped per organization each day.

Never — not available over MCP

• Publishing, pausing, or editing ads, or changing budgets, on any ad platform.
• Deleting data, or changing integrations, credentials, billing, or subscription settings.
• Inviting, removing, or changing the roles of users.
• Accessing organizations you are not an active member of.

04 Your controls

As a user

• Choose whether to connect. MCP access exists only after you connect an assistant and sign in to AdsViewer. A hosted assistant also needs your approval on the consent screen.
• Nothing changes without you. Drafts are never applied over MCP. You make any change yourself in AdsViewer.
• Per-tool permissions in your assistant. Most MCP clients let you allow, block, or require confirmation for each tool. You can use this, for example, to keep a connection read-only or to require a prompt before media generation.
• Disconnect at any time. Remove the connector in your assistant. To revoke its access on our side as well, contact info@adsviewer.io.

As an organization admin or IT team

• Membership is the boundary. Removing a user from an organization in AdsViewer ends their assistant's access to that organization.
• Automation permissions carry over. Only users who can manage automations in AdsViewer can draft automations over MCP.
• Organization-level requests. To revoke tokens or get a record of MCP activity for a security review, contact info@adsviewer.io.

05 Data handling

• Data the assistant requests is returned to the AI client you connected, and is processed by that client's provider under your agreement with them. Review their data-retention and training policies, as you would for any other tool you use.
• The MCP server does not send your advertising data to any additional AI model to answer requests. Prompts for image and video generation are sent to our media-generation provider.
• We log MCP requests, including the user, organization, and tool used, to keep the service secure and operating reliably. These logs are handled in line with our Privacy Policy.
• Use of the MCP server is subject to our Terms of Service.

06 Questions

For security questionnaires, vendor reviews, or anything not covered here, contact info@adsviewer.io.