Wherobots

com.wherobotsPublished by wherobots.comOfficial publisherv0.1.0Updated Oct 24, 2026

Generate and run high performance queries on open and private spatial data at-scale in the cloud

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Lets an assistant generate and run high-performance spatial data queries at scale on open and private data in the Wherobots cloud.

What you can do
This remote MCP server connects an assistant to Wherobots, a cloud platform for spatial analytics. According to its description, it lets the assistant generate and run high-performance queries on open and private spatial data at scale. No individual tools are listed in the supplied material, so the exact operations available are not documented here.
When to use it
Relevant when you work with geospatial datasets in the Wherobots cloud and want an assistant to help compose and execute spatial queries against them, including large or private datasets.
Requirements
A remote endpoint at api.cloud.wherobots.com over streamable HTTP. Authentication is required via OAuth, and an API key is supplied in the X-API-Key header. A Wherobots account and network access are needed.
Before you install
The server requires a Wherobots API key sent in the X-API-Key header; treat it as a secret. Queries run against your cloud data and may read private spatial datasets, so confirm what the assistant is allowed to query before use.

Installation

In SourceWeft

  1. Open Wherobots 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/com.wherobots%2Fmcp-server/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": {
    "wherobots": {
      "type": "http",
      "url": "https://api.cloud.wherobots.com/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.0LatestSep 16, 2026

Score

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

    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.