QueryScope

dev.queryscopePublished by queryscope.devOfficial publisherv1.0.0Updated Oct 24, 2026

Search Console in your AI IDE: the plan, stored history, and a measured record of every change.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

QueryScope is a remote MCP server that brings Search Console into an AI IDE, with the plan, stored history and a measured record of every change.

What you can do
Connect an assistant to Search Console data from inside an AI IDE, with OAuth sign-in to a hosted endpoint. Work from a plan and stored history of changes rather than one-off queries. Review a measured record of every change made. No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when you want an assistant to work with Search Console inside an AI IDE and to keep a traceable history of changes, rather than running isolated lookups.
Requirements
A remote streamable HTTP endpoint at mcp.queryscope.dev; no local package or runtime is needed. OAuth authentication is required. No environment variables or headers are declared.
Before you install
The server requires OAuth access to your account, so review the scopes it requests before authorizing. It keeps a record of changes, which implies it may write or modify data; confirm what it can change before use. No tool list is published, so verify its actions after connecting.

Installation

In SourceWeft

  1. Open QueryScope 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/dev.queryscope%2Fmcp/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": {
    "queryscope": {
      "type": "http",
      "url": "https://mcp.queryscope.dev/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 13, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.