Adjoin documentation: connect Google Ads, Meta Ads and Clarity to your MCP client

Your MCP endpoint is https://adjoin.ae/mcp. It uses OAuth 2.1: the AI client registers itself, you sign in to Adjoin and approve, and the client receives short-lived tokens. Nothing to copy except the URL.

Claude

  1. Settings → Connectors → Add custom connector.
  2. Name: Adjoin. URL: https://adjoin.ae/mcp.
  3. Connect, sign in, Allow.

Claude Code

claude mcp add --transport http adjoin https://adjoin.ae/mcp

ChatGPT

  1. Settings → Connectors → Advanced → Developer mode.
  2. Create a connector with the URL above and OAuth authentication.
  3. Sign in, Allow.

Connect your platforms

Each connection is verified live before it is saved, encrypted at rest, and only ever used to read. You can replace or disconnect any of them from Connections.

Meta Ads: system user token

A system user is a non-human login inside your Meta Business portfolio. Its token lets Adjoin read the ad accounts you assign to it, and nothing else.

  1. Open Business Settings and make sure the right business portfolio is selected at the top left.
  2. Go to Users → System users. If there is none, click Add, give it a name such as "Adjoin reader" and the Employee role.
  3. Select the system user and click Assign assets. Choose Ad accounts, tick every account you want your AI to see, and grant View performance only.
  4. Click Generate token. Pick any app in the portfolio, set the expiry to Never, tick only ads_read, and generate.
  5. Copy the token straight away (Meta shows it once) and paste it into Connect Meta Ads.

If Adjoin reports zero reachable accounts, step 3 was skipped: assign the ad accounts and generate a fresh token.

Google Analytics: add a Viewer

No token and no OAuth. Adjoin has a Google service account; you give it read access to your GA4 property and tell Adjoin the property id. The email to add is shown on the Connect Google Analytics page.

  1. In Google Analytics, open Admin (bottom left) and pick the property.
  2. Under Property, open Property access management, click + → Add users, paste Adjoin's service account email, choose the Viewer role, untick "Notify by email", and add.
  3. Still under Property, open Property details and copy the Property ID (a number such as 123456789; not the G-XXXX measurement id).
  4. Paste the id into Connect Google Analytics. Several properties: add the Viewer on each and list the ids separated by commas.

Access takes effect within a minute or two. If Adjoin reports "access denied", check the email was added at the property level (not only on a data stream or account).

Google Search Console: add a user

  1. In Search Console, pick the property, then Settings → Users and permissions → Add user.
  2. Paste Adjoin's service account email (shown on the Connect Search Console page) with permission Restricted, which is read-only.
  3. Enter the property in Connect Search Console exactly as Search Console names it: sc-domain:example.com for a domain property, or https://example.com/ for a URL-prefix property. Several: separate with commas.

Search Console data is final about two days after the fact, so date presets end two days ago.

Microsoft Clarity: Data Export token

  1. Open Clarity and pick the project for your site.
  2. Go to Settings → Data Export and click Generate new API token. Give it a name such as "Adjoin".
  3. Copy the token and paste it into Connect Microsoft Clarity.

Clarity allows 10 Data Export calls per project per day and up to 3 days of data per call. Adjoin caches responses for an hour so a conversation does not burn through the limit.

Google Ads: bring your own credentials

Google Ads needs three things from you: a developer token, an OAuth client of your own, and a refresh token minted for that client. Each takes a few minutes.

1. Developer token

  1. In Google Ads, open Tools → API Center (you need a manager account for this).
  2. Copy the developer token. Check the access level: it must be Basic or Standard. A Test token only works against test accounts, so apply for Basic access there if you have not already.

2. OAuth client

  1. In Google Cloud → APIs & Services → Credentials, create an OAuth client ID of type Web application.
  2. Add https://developers.google.com/oauthplayground as an authorised redirect URI. Save the client ID and client secret.
  3. Under Enabled APIs, make sure Google Ads API is enabled for the project.

3. Refresh token

  1. Open the OAuth 2.0 Playground, click the gear icon, tick Use your own OAuth credentials and paste the client ID and secret.
  2. In step 1, enter the scope https://www.googleapis.com/auth/adwords and click Authorize APIs. Sign in with the Google account that has access to your ads.
  3. In step 2, click Exchange authorization code for tokens and copy the refresh token.

Paste all of it into Connect Google Ads. Add your manager (MCC) customer ID if you reach the accounts through one, and the default customer ID your AI should use when you do not name an account.

Tools

All tools are read-only. See the full list in your dashboard once signed in.