Remote MCP with OAuth
Paste this URL into your assistant's remote MCP connector setup. Sign in through the VaanarStack authorization screen; you do not need to paste advertising credentials or API keys into chat.
// VaanarStack Apps · MCP connection guide
For agencies and in-house marketing teams: connect an MCP-compatible assistant to your VaanarStack workspace, explore audit findings and investigate the next question without copying reports into chat.
https://apps.vaanarstack.com/mcp
Paste this URL into your assistant's remote MCP connector setup. Sign in through the VaanarStack authorization screen; you do not need to paste advertising credentials or API keys into chat.
Sign in with the email that has access to the relevant VaanarStack workspace. For an agency, use the workspace containing the client brands you are authorized to work with.
Completed audits can be read once your workspace and account are available. Account connection or setup may require additional permission and a separate advertising-platform authorization step.
The assistant must support a remote MCP server with OAuth. Organization-managed accounts may require an administrator to enable custom connectors.
Use Claude's custom remote connector flow. Labels may vary between web and desktop versions.
In Claude, open Settings, then Connectors. Choose Add custom connector. If your organization manages connectors, ask its administrator to enable this connector.
Enter VaanarStack Apps as the name and https://apps.vaanarstack.com/mcp as the remote MCP server URL. Save or add the connector.
Choose Connect if prompted. On the VaanarStack authorization screen, sign in using the email associated with your workspace. If the wrong account is shown, use Switch account.
Read the permissions requested by your assistant and authorize the access you intend to use. Additional setup or live-data capabilities depend on the scopes requested and approved.
Return to Claude and make the VaanarStack connector available in your conversation. Start by asking it to identify your accessible workspace, brand and attached advertising account.
Show the VaanarStack workspaces and brands I can access. Resolve the advertising account for [client brand] before querying its data.
Summarise the latest completed Google Ads or Meta Ads audit for [brand]. Tell me the reporting window, the main findings and the evidence supporting them.
Help me prepare a client review from this audit. Separate observations, hypotheses and recommended next steps, and flag missing evidence.
For the resolved account, explain what evidence is available to investigate the change in cost per result. Ask before any action that requires my confirmation.
Access depends on your workspace membership, account bindings and the permissions approved during connection. It cannot edit campaigns, bids, ads or budgets.
Explore available Google Ads and Meta Ads audit findings, reporting windows and supporting artifacts.
With the appropriate permissions, query retained evidence and supported read-only advertising data. Live-data requests are bounded; the connector reports applicable usage and limits.
Additional permissions can support account setup, a confirmed first audit for an eligible directly connected account, workspace invitations and confirmed feedback submission. These are separate from read-only campaign analysis.
Confirm that you signed in with the correct workspace email and that the brand and advertising account are attached. Ask the assistant to resolve the workspace and brand first. A missing brand requires setup; repeating a data query will not create it.
A connection does not mean an audit already exists. Check the account setup and whether a completed audit is available. First-audit setup is available only for eligible accounts and approved permissions; the assistant should explain the next action and ask for confirmation where needed.
Your session or permission grant may need refreshing, or the assistant may be requesting additional capabilities. Review the VaanarStack authorization screen before reconnecting.
Use the same server URL in a client that supports remote MCP and OAuth. Its setup screens and supported permissions may differ. The Claude steps above are not a claim that every other client has been tested.
Disconnect or remove VaanarStack in your assistant's connector settings. Contact VaanarStack if you need help reviewing workspace access or authorization.
Share the step where setup stopped and the error message. Do not send passwords, tokens or advertising credentials.