Querya · Developers

Querya API and MCP developer resources

Use Querya's hosted MCP server to connect an AI assistant to Google Ads accounts chosen by the user. Start with the remote endpoint https://mcp.querya.io/mcp, then complete Google sign-in and account authorization.

Quickstart and reference

Accounts and authentication

The MCP server uses OAuth rather than a newly generated developer API key. Dashboard REST requests use the authenticated Querya session cookie. Manage selected accounts and change permissions in the dashboard. Never place session cookies or OAuth tokens in prompts, public code or shared documents.

Safe testing

Start with read-only reporting on an account you are authorized to access. Do not treat a change preview as a separate sandbox: previews validate a proposed write, and applying it still requires explicit user approval. This site does not provide a separate public sandbox environment or a CLI package.