Your assistant reads your accounts. When it acts, Pilot sets the guardrails.

By the Pilot team at Braike · Updated

Pilot MCP gives ChatGPT, Claude or your own assistant access to 28 connectors: 16 ad platforms, Google Analytics 4, Search Console, Tag Manager, Merchant Center, Business Profile, and your SEO, CRM and content tools; read-⁠only on the Free plan, and acting too at €29. Your ad platform access stays encrypted at Pilot, and you revoke the assistant's access whenever you want.

The path of your data, on every question

Your assistantClaude, ChatGPT…
  • ChatGPTin the plugins
  • Claudecustom connector
  • Codex, Cursor, VS Codeat the same address
  • Your in-⁠house assistantauthorization or access key

It gets the access your plan gives, for the workspace you choose, and the result of each tool.

Pilot MCPset by your plan
app.pilot.braike.com/mcp
  • Reads on Free, acts at €29, one object at a time
  • Adds your ad platform access itself, on every call
  • Only touches the authorized workspace's accounts
  • Rechecks your role on every call
  • Logs every call
Your sources28 sources

Ad platforms16

  • Google Ads
  • Meta Ads
  • TikTok Ads
  • LinkedIn Ads
  • Microsoft Advertising
  • Pinterest Ads
  • Snapchat Ads
  • Amazon Ads
  • Apple Ads
  • Reddit Ads
  • Spotify Ads
  • Uber Ads
  • OpenAI Ads
  • Display & Video 360
  • Search Ads 360
  • Campaign Manager 360

accounts linked to the workspace

Measurement5

  • Google Analytics 4
  • Google Search Console
  • Google Tag Manager
  • Google Merchant Center
  • Google Business Profile

properties, sites, containers, accounts and listings linked to the workspace

Your tools7

  • Semrush
  • DataForSEO
  • Salesforce
  • Sellsy
  • WordPress
  • Magento
  • PBS Media Manager

with your own access, and your own credits for Semrush and DataForSEO

Your access to these sources stays encrypted at Pilot: your assistant never sees it.

Never sent to your assistant
  • Your ad platform accesskept encrypted at Pilot
  • Tokens and secretsno served tool returns them
  • Your customers' personal datacustomer lists, contact and lead records, user-⁠level exports
  • Other members' emails, documents and calendarsa personal connector only serves the person who connected it
On every question, your assistant calls a Pilot MCP tool. Pilot checks the access and the accounts requested, reads the ad platform or the overnight data with the access it holds, and returns only the result.

Six guarantees, checkable in the documentation.

They do not depend on your assistant: Pilot enforces them, on every call.

Pilot MCPon every call
  • Read or act: your plan decides

    On the Free plan, your assistant only has read tools: even if a hidden instruction in content it reads tried to hijack it, it would find no tool to change a campaign. At €29, it creates, edits, pauses and deletes, one object at a time, never in bulk, and Pilot re-⁠reads the object before and after.

  • Your access stays with Pilot

    The access your ad platforms gave Pilot is encrypted, and Pilot adds it itself on every call. No served tool asks for or returns a token or a secret.

  • Your workspace, nothing more

    Your assistant reads only the accounts, properties and sites linked to the workspace you authorized, even when a platform's access sees more, such as an agency's whole portfolio.

  • Nothing personal, except your own

    Never customer lists, contact or lead records, or user-⁠level exports. Your emails, documents and calendars are served only to you, if you connect them yourself, never to the other members of the workspace.

  • Access you revoke

    You authorize the workspace of your choice, then revoke access from Pilot whenever you want. Pilot rechecks your role on every call: someone removed from the workspace loses access on the next call.

  • Every call is logged

    The tool, the ad platform, the result, the duration, the app and the person. For a change, Pilot also keeps the object as it was and as it became. Workspace admins read this log in Pilot, which keeps it for 12 months.

Your in-⁠house assistant connects too.

An in-⁠house agent, an automation tool, a team script: if it speaks MCP, it connects to Pilot like ChatGPT or Claude, with the same access, the same scope and the same log.

With an access key

  • The key is shown only once: Pilot keeps only a fingerprint of it, never the key itself.
  • Its role never exceeds that of the person who created it.
  • It stops working if that person leaves the workspace.
  • It does not expire on its own: revoke it as soon as it is no longer used.
  • Its calls are logged, just like ChatGPT's and Claude's.
Connect your tooltwo ways

The usual authorization

If your tool can sign in on its own, it goes through the same authorization as ChatGPT and Claude, at the same address: you choose the workspace, then authorize the access your plan gives.

https://app.pilot.braike.com/mcp

An access key

Otherwise, a workspace admin creates a key in Pilot, in the “For developers” block. It opens that workspace, and that workspace only.

You see every call, and you revoke access.

In Pilot, your workspace's “Claude & ChatGPT” page shows who can query it and what your assistants read.

  • Active access

    Every app and every access key, its level, who connected it. Everyone removes their own access there, an admin anyone's in the workspace.

  • Recent activity

    The latest calls, in plain sentences, Pilot's refusals included, for example on an account outside the workspace. Admins only.

  • For developers

    The full log, call by call, and the access keys.

Claude & ChatGPT · Active accessLumio Sneakers

The apps that can query this workspace, and at what level.

  • ClaudeRead

    Connected by Léa on Oct 21, 2026 · used 3 min ago

    Remove
  • ChatGPTRead

    Connected by Léa on Oct 28, 2026 · used yesterday

    Remove
  • In-⁠house assistantRead

    Access key created by Léa on Oct 30, 2026 · used 2 h ago

    In-⁠house assistant will no longer be able to query this workspace.Remove accessCancel
Claude & ChatGPT · Recent activityadmins
  • Claude read the cross-⁠platform overview3 min ago
  • Pilot refused Google Ads · get campaign performance to ChatGPT1 h ago
  • In-⁠house assistant read Google Ads · get search terms report2 h ago
  • ChatGPT read budget pacingyesterday
  • Claude read data freshnessyesterday
Illustration of Pilot's “Claude & ChatGPT” page, with sample data: Lumio Sneakers is a fictitious brand.

Hosted with the rest of Pilot, in Europe.

Pilot MCP is not a separate service: it runs in the same application and the same database as Pilot. What your assistant then does with the numbers it receives depends on its provider, OpenAI for ChatGPT or Anthropic for Claude, and on its terms.

All of Pilot's security
Pilot's side

European servers

Pilot's application and database, where Pilot MCP, its log and the overnight numbers live, run in Europe.

Encrypted access

Your ad platforms connect to Pilot through their official authorization page: Pilot never sees your passwords, and encrypts the access they give it.

A log kept 12 months

The log of your assistants' calls is erased after 12 months. A workspace unused for 12 months has its data deleted.

Security questions

Yes, on the €29 plan: your assistant creates, edits, pauses and deletes, one object at a time, never in bulk. No access level to pick: your plan decides. The change applies directly in the ad platform: Pilot only touches your workspace's accounts, re-⁠reads the object before and after, and logs every call. On the Free plan, it only reads.

Connect your assistant, with Pilot's guardrails.

Pilot is in ChatGPT's plugins and is added to Claude by its address. One authorization, and your assistant reads your accounts; at €29, it also acts, one object at a time.