# Get started

Source: https://pilot.braike.com/en/docs/demarrer

Create your Pilot MCP account, connect your ad platforms, choose your accounts, then connect your assistant.

Four steps separate sign-up from your assistant's first answer: connect an ad platform, choose the accounts, connect an assistant, ask a first question. Your workspace console shows them under **Getting started** and checks each one off when it is done.

## Create your account [#compte]

Sign-up starts at [app.pilot.braike.com/commencer?offre=mcp](https://app.pilot.braike.com/commencer?offre=mcp), or from the invitation link you received, which leads there with its code. You create your account with your email address and a password, or with Google.

Depending on how sign-ups are opened, the offer is open to everyone or by invitation only. Pilot then creates your first workspace and guides you step by step to that workspace's console, the **Claude & ChatGPT** page.

<Callout title="What is a workspace?">
A Pilot workspace groups ad accounts, the people who have access to it, and the assistants authorized to read it. An agency often opens one per client; an advertiser, just one. An assistant authorized on a workspace only reads that workspace.
</Callout>

## The four steps [#etapes]

<Steps>
<Step>

### Connect an ad platform [#regie]

In **Connectors**, connect Google Ads, Meta Ads, Google Analytics or Search Console. You sign in with the platform, which gives Pilot an access. Pilot keeps it encrypted; your assistant will never see it.

</Step>
<Step>

### Choose the accounts [#comptes]

Pick the accounts, properties or sites your assistants may read. Only those are attached to the workspace: an access that sees an agency's whole portfolio only serves what you chose. See [Account scope](/en/docs/perimetre-des-comptes).

</Step>
<Step>

### Connect an assistant [#assistant]

Add Pilot to Claude, ChatGPT, Cursor or VS Code, then authorize access to your workspace. The steps, client by client, are on [Connect your assistant](/en/docs/brancher-son-assistant).

</Step>
<Step>

### First call verified [#appel]

Ask your assistant a question, for example "Which campaigns spent without converting this week?". Its first call checks off the last step. The console's **Test** button also checks the service end to end.

</Step>
</Steps>

## What the console shows [#console]

Your workspace console, the **Claude & ChatGPT** page, gathers what to keep an eye on:

- the **service status**, checked on demand: address reachable, secure connection, subscription, session opening, tools available, one metric read;
- the **active access** list: the assistants connected to the workspace, their level, and the button to remove one;
- the **recent activity**, for admins: what each assistant looked at;
- **Your usage this month** and **Your plan**: tool calls, ad accounts, people;
- the **workspace address** and the access keys, in **For developers**.

## After the first call [#ensuite]

- Ad platform tools query the platform live, on every call.
- Pilot's analyses, such as the cross-platform view or budget pacing, read the data Pilot collects every night for the accounts your assistants query. See [Limits and plans](/en/docs/limites-et-forfaits#collecte).
- To go faster, install a [skill](/en/docs/skills): your assistant then follows a proven method, with the right tools.