Connecting Skai MCP servers

It depends on the MCP they connect, but access is always scoped to whatever that individual user's own Skai login already permits. Connecting through an AI assistant doesn't grant anyone new data access, it only exposes what they could already see or do by logging into Skai directly.

The Campaign Actions Connector can adjust bids, budgets, and statuses, but every change is meant to go through a preview-and-approve step first. Skai's own guidance is: "We strongly recommend previewing and approving all updates made via this MCP by a person. Working with your agent in Auto Mode is not recommended." The Reporting Connector has no write capability at all. The Insights Connector cannot touch bids, budgets, or statuses either; it surfaces recommendations, and separately can set up experiments, creative variations, and notification rules.

NB1XppreF8kHUVpRtrQKksayoedpfatm. It goes wherever your platform's connector setup asks for a Client ID. Claude, ChatGPT, and Gemini Enterprise all use this same value. Cursor, VS Code, and other header-based clients use a personal access token instead and don't need it.

Skai meets some of the most stringent security and compliance standards in the industry, and we're glad to complete additional security or compliance documentation as needed. The fastest way to get a straight answer for your organization is to contact us directly, your Skai account team can walk through any infosec or compliance questions with you.

Your organization's existing Skai account or customer success contact is the fastest path. If you don't have one, skai.io has general contact information.

You're probably here because a user in your organization is trying to connect Skai's MCP servers to their AI assistant (Claude, ChatGPT, Gemini, or similar) so it can pull reporting or stage changes for them. On some platforms, adding a custom connector is gated behind an org or workspace admin, and that's you, so they were told to loop you in rather than guess at it themselves.

Today, Skai clients have unlimited access to the Skai Reporting Connector for no additional cost. Campaign Actions Connector access is unlimited at no additional cost for Skai clients with a platform license agreement, subject to an additional legal amendment. The Insights Connector is newer and still in beta, so confirm its terms with your account team rather than assuming they match either of the other two. Please check with your Skai account team to confirm any specific requirements are met.

Each person authenticates individually, either through Skai's own OAuth sign-in or their own personal access token (valid 90 days, renewed at login.kenshoo.com). There's no single shared org-wide credential, so what any one person's AI assistant can see or do is exactly what that person could already see or do by logging into Skai themselves.

Usually not. Those read a small config file with the developer's own personal access token, on their own machine, so there's typically no org-wide switch to flip. The platforms that do need something from you are the ones with a central connector or app allowlist: Claude (Team/Enterprise), ChatGPT (Business/Enterprise/Edu), and Gemini Enterprise via Google Workspace.

Since every connection rides an individual's own Skai login or personal access token, revoking that person's Skai account access (or declining to help them renew an expired token) ends their MCP access the same way it would end any other integration. Removing Skai from your platform's connector allowlist, where one exists, also stops any new connections.