MCP.so
Sign In

GridWhy MCP ServerVerifiedFeatured

@GridWhy

Basic information

Transport

Streamable HTTP

Authentication

OAuth

Last updated

Category

Data & Analytics

Author

GridWhy

Submitted by

Fuat Sezer

About GridWhy MCP Server

Google Maps geo-grid rank tracking for local SEO agencies. Ask your AI assistant which locations dropped, why a ranking changed (competitors that rose, review velocity, category or name changes) with client-ready lines and next steps, or run a new grid scan.

#local seo#google maps#rank tracking#geo-grid#seo#marketing#agency

Connection details

https://gridwhy.com/mcp

Setup

claude mcp add gridwhy --transport http https://gridwhy.com/mcp

GridWhy MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

This server requires authentication. Tool discovery may require signing in or credentials from the provider.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

What is GridWhy?

GridWhy tracks where a business ranks on Google Maps from a grid of points around it, on a fixed weekly schedule, and explains every change. It is built for local SEO agencies.

Tools

  • get_history: locations, tracked keywords and their scans: how many grid points rank in the top 20 and top 3, average and best rank, a one-line "what changed", and a report link.
  • explain_change: why a ranking changed between two scans (coverage, competitors that rose or appeared, review velocity, rating, category or name changes), each with a line to paste to the client, plus next steps.
  • run_scan: start a grid scan for a tracked keyword now. Takes 15-30 seconds; then call explain_change.

Example prompts

  • "Which of my locations lost map pack visibility this week, and why?"
  • "Show the grid history for 'plumber' at Rooter-Man Plumbing."
  • "Run a scan for 'drain cleaning' and tell me what changed."

Authentication

Connect with OAuth (your client is prompted to sign in), or send Authorization: Bearer <API key> with a key from GridWhy settings.

Pricing

MCP is included on every plan. Plans start at $29/month with a 14-day free trial, no card required. Docs: https://gridwhy.com/docs/mcp

Frequently asked questions

1

What is the GridWhy remote MCP server?

The GridWhy remote MCP server is a hosted Model Context Protocol endpoint at https://gridwhy.com/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the GridWhy MCP server?

Add the endpoint https://gridwhy.com/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the GridWhy MCP server require authentication?

Yes. GridWhy uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

4

Which transport does the GridWhy MCP server use?

GridWhy exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments