TikTok Ads is coming to Adrails

Perplexity integration

Meta Ads and Google Ads in Perplexity

Perplexity connects to the Adrails MCP server as a remote connector. After OAuth sign-in, you choose one workspace and the permissions it can use, then Perplexity can read your Meta Ads and Google Ads data, explain results and prepare a controlled change for review in Adrails.

01

What Perplexity can do on your ad accounts

Ask Perplexity for an account review with the exact period, metric and account selection you need. Adrails returns spend, results, revenue, ROAS, CPA, CTR, CPM, reach and frequency from the workspace, while Perplexity explains the evidence in the conversation.

For an operational request, Perplexity can prepare a launch, a pause, a split test, an edit or a budget move within the product limit. The result is a proposal with the before and after values and a link to Adrails. It is not a live advertising change until an owner or admin reviews and applies it there.

  • Read account, campaign, ad set and ad performance
  • Compare periods and prepare a data-backed next action
  • Keep every platform write behind review in Adrails

02

How to connect Perplexity

Perplexity adds Adrails as a custom remote MCP connector. The server is public over HTTPS and uses Streamable HTTP with OAuth, so there is no provider credential, API key or client secret to copy into Perplexity.

Select the Adrails connector to complete sign-in, choose one workspace and only the permissions you intend to give. Removing the connector in Perplexity does not revoke the Adrails grant, which you can revoke under Your connections.

  • 1. In Perplexity, open Plugins, or Customize then Connectors
  • 2. Choose Add custom, Add MCP connector, then Remote. Name it Adrails and enter https://adrails.ai/api/mcp
  • 3. Under Advanced, choose OAuth and Streamable HTTP, acknowledge the connector notice and add it
  • 4. Select Adrails, complete sign-in and enable it in your conversation

What runs where

Perplexity, Adrails and the ad platform, step by step

Perplexity, Adrails and the ad platform, step by step
StepIn PerplexityIn Adrails
A question about resultsPerplexity picks the tool and reasons over the figuresReads the workspace's accounts and returns the table; nothing changes on the platform
A new launchlaunch_brief asks what is missing, then campaigns_launch or google_ads_build prepares itThe proposal waits on the Review advertising change page; applied, it is built paused
A pause or a budget moveOne exact change, prepared in the conversationAn owner or admin applies it after Adrails reads the platform again; undo while it still matches
The permission promptPerplexity's own setting for tool callsThe consent screen: one workspace and the permissions you grant
The recordThe conversationEvery tool call logged, every change kept with its evidence
The costYour Perplexity plan does the reasoning0 credits per tool call; paid plans from $49 a month to apply changes

From the Adrails MCP documentation and Perplexity's own documentation on 4 October 2026.

Common questions

Does Perplexity need an API key for Adrails?

No. Add the Adrails MCP server as a remote connector and select OAuth. You sign in to Adrails, choose a workspace and grant only the permissions you need.

Can Perplexity apply a change to my ad account?

No. Perplexity can prepare a proposal through Adrails. An owner or admin reviews the proposal on its Adrails page, where the platform is read again before the exact change can be applied.

Which ad platforms can Perplexity work on?

Meta Ads and Google Ads, across the accounts in the workspace you selected during sign-in.

How do I remove Perplexity access to Adrails?

Remove the connector in Perplexity, then revoke its grant from Your connections in Adrails if you no longer want it to access the workspace. Revoking the grant takes effect for future tool calls.