QueryAtlas

app.queryatlasPublished by queryatlas.appOfficial publisherv0.1.0Updated Oct 30, 2026

Query selected Google and Bing analytics, search, and advertising reports through MCP.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Remote MCP server that lets an assistant query selected Google and Bing analytics, search, and advertising reports.

What you can do
  • Query selected Google and Bing analytics reports
  • Query selected Google and Bing search reports
  • Query selected Google and Bing advertising reports
  • No tool list is published, so the exact operations are not documented in the available material.
When to use it
Useful when you want an assistant to pull marketing performance data from Google and Bing analytics, search, and advertising accounts without leaving the conversation.
Requirements
A remote streamable HTTP endpoint at queryatlas.app; no local package or runtime is needed. OAuth authentication is required, so the user must sign in and authorize access to the relevant Google and Bing accounts.
Before you install
OAuth grants the server access to Google and Bing analytics, search, and advertising data, which may include business performance and account information. The available material does not describe which reports are exposed, whether any tool writes or changes data, or how data is handled, so review the provider's terms before connecting.

Installation

In SourceWeft

  1. Open QueryAtlas in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.queryatlas%2Fqueryatlas/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "queryatlas": {
      "type": "http",
      "url": "https://queryatlas.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 30, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.