Querya

Querya Developer Documentation

Querya is a hosted MCP server for Google Ads. Connect a compatible AI client with OAuth, choose the accounts it can access, and ask for reporting, keyword research or a proposed change.

Connect in Claude

https://mcp.querya.io/mcp

  1. Open Settings > Connectors > Add custom connector in Claude.
  2. Paste https://mcp.querya.io/mcp as the connector URL.
  3. Sign in with Google. The Google screen shows Filtripixel, the Extractify app that also runs Querya.
  4. Choose the Google Ads accounts to connect and whether changes are allowed on each account.
  5. Use Querya in any chat.

The same URL works in ChatGPT and Cursor. Use a client that supports remote MCP with Streamable HTTP and OAuth.

Prerequisites

A Google account with access to at least one Google Ads account. Changes require Pro or Max, plus write permission for the selected account.

Plans

Selecting or reconnecting an account does not reset the rolling usage window. Compare plans or manage your plan and billing.

Example prompts

How changes work

  1. Every change returns a preview validated by Google Ads, including the risk level and spend impact.
  2. Nothing is applied until you confirm in the chat.
  3. New campaigns are always paused. Guardrails cap budgets and bids.
  4. Every change is logged and can be undone.

OAuth scopes and account permissions

The MCP protected-resource metadata advertises these scopes:

Read the machine-readable OAuth resource metadata. Connect only accounts the user selected. A write scope does not replace the account-level permission or per-change confirmation.

When to use Querya

REST API

AI assistants connect through MCP at https://mcp.querya.io/mcp. You do not need to call the REST API to use Querya in a chat.

The Querya dashboard uses https://api.querya.io/v1. Account data and actions require a signed-in session using the qy_session cookie. Browser requests must include credentials; write requests must come from Querya's own origin. A 401 response means you need to sign in again.

The authoritative OpenAPI specification is public; this does not make account data public. A local mirror is also available as an older snapshot; consult the live specification for the current contract.

Dashboard endpoints

  • GET /v1/me — current user, plan and Google connections.
  • GET /v1/accounts — list connected Ads accounts.
  • PUT /v1/accounts — replace enabled accounts and their write permissions.
  • DELETE /v1/connections/{id} — disconnect a Google login.
  • POST /v1/logout — end the dashboard session.

MCP authorization endpoints

  • GET /v1/connect/request — read the pending account authorization request.
  • POST /v1/connect/approve — approve selected accounts.
  • POST /v1/connect/deny — deny the authorization request.

Disconnect / revoke access

Send data deletion requests to suporte@extractify.com.br.

Troubleshooting

Other resources

Querya is an independent product and is not affiliated with Google.