Localseodata

io.github.localseodataPublished by GitHub account localseodatav1.1.0Updated Oct 24, 2026

53 local SEO data tools: rankings, reviews, audits, keywords, AI visibility.

VerifiedSTDIODesktop onlyWeb Search & Scraping Data & Analytics Business & Commerce

Server details

Identifier: io.github.localseodata/mcp-server
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account localseodata for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.localseodata%2Fmcp-server.svg)](https://sourceweft.com/mcp/io.github.localseodata%2Fmcp-server?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local SEO Data MCP server giving assistants 53 tools for local search rankings, reviews, audits, keywords, geogrids and AI visibility.

What you can do: Look up SERP and map rankings, local pack, Apple Maps, Bing local and business profiles
Check reviews, review velocity, Q&A, listings and profile health across platforms
Research keywords: search volume, suggestions, related terms, trends and site keywords
Run local, citation, reputation and page audits, plus competitor ads, backlinks and brand mentions
Score AI visibility across ChatGPT, Gemini, Perplexity, Claude and Google AI Overviews
Run geogrid scans, build gap and opportunity reports, and check account credit balance
When to use it: Useful for SEO consultants, agencies and local business owners who want an assistant to answer ranking, review, audit and keyword questions for specific businesses and locations, or to track how AI assistants recommend a business.
Requirements: An account at Local SEO Data and either OAuth sign-in through the hosted endpoint or an API key (sk_live_ prefix) passed in the URL or as a Bearer header. Self-hosting needs Node.js and npm, or Docker; optional variables include API_BASE_URL, PORT, OAUTH_ENABLED, OAUTH_ISSUER and MCP_RESOURCE_URL. Network access to the Local SEO Data API.

Before you install

Most tool calls spend credits from your Local SEO Data account, so usage costs money; only a few tools are free. The API key is placed in the server URL for some clients, and the README says to treat such a URL like a password. Queries and business details are sent to the Local SEO Data API and hosted endpoint. Keys can be revoked in the dashboard.

Installation

In SourceWeft

Open Localseodata in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Local SEO Data MCP Server

Model Context Protocol server for Local SEO Data. It gives AI assistants 53 local SEO data tools: SERP and map rankings, reviews, audits, keyword research, competitor analysis, geogrid tracking, and AI visibility scoring.

Connect once, then ask questions in plain English. Your assistant picks the right tools.

Endpoint: https://mcp.localseodata.com/mcp (streamable HTTP)
Docs: localseodata.com/docs/mcp-server
Privacy policy: localseodata.com/privacy

Setup (OAuth, recommended)

Add https://mcp.localseodata.com/mcp as a connector in your client and click Connect. You'll be asked to sign in to Local SEO Data (or create an account) and approve access. You don't need to copy an API key.

Claude (claude.ai, Claude Desktop, mobile)

Open Settings → Connectors → Add custom connector.
Enter a name (e.g. Local SEO Data) and the URL https://mcp.localseodata.com/mcp.
Click Add, then Connect, and sign in.

Claude Code

Then run /mcp in Claude Code, select localseodata, and choose Authenticate.

ChatGPT and other OAuth-capable clients

Add a custom connector or remote MCP server with the URL https://mcp.localseodata.com/mcp and click Connect. Any client that supports MCP authorization will start the sign-in flow on its own.

Fallback: API key in the URL

If your client can't do OAuth, pass an API key in the URL instead:

Sign up at localseodata.com/signup.
Create a key in your API Keys dashboard. Keys start with sk_live_.
Use https://mcp.localseodata.com/mcp?key=YOUR_API_KEY as the server URL.

Example configs:

Cursor (.cursor/mcp.json or ~/.cursor/mcp.json)

json

{  "mcpServers": {    "localseodata": {      "url": "https://mcp.localseodata.com/mcp?key=YOUR_API_KEY"    }  }}

{  "mcpServers": {    "localseodata": {      "url": "https://mcp.localseodata.com/mcp?key=YOUR_API_KEY"    }  }}

VS Code (GitHub Copilot) (.vscode/mcp.json)

json

{  "servers": {    "localseodata": {      "type": "http",      "url": "https://mcp.localseodata.com/mcp?key=YOUR_API_KEY"    }  }}

{  "servers": {    "localseodata": {      "type": "http",      "url": "https://mcp.localseodata.com/mcp?key=YOUR_API_KEY"    }  }}

Windsurf (~/.codeium/windsurf/mcp_config.json)

json

{  "mcpServers": {    "localseodata": {      "serverUrl": "https://mcp.localseodata.com/mcp?key=YOUR_API_KEY"    }  }}

{  "mcpServers": {    "localseodata": {      "serverUrl": "https://mcp.localseodata.com/mcp?key=YOUR_API_KEY"    }  }}

Cline: Settings → MCP Servers → Add Remote Server, with the URL https://mcp.localseodata.com/mcp?key=YOUR_API_KEY.

You can create or revoke keys at any time in the API Keys dashboard. Treat a URL that contains your key like a password.

Available tools

53 tools in total:

Category	Tools
SERP data	`local_pack`, `organic_serp`, `maps`, `local_finder`, `local_services_ads`, `ai_overview`, `ai_mode`
Other platforms	`apple_maps`, `apple_business_profile`, `bing_local`, `bing_business_profile`
AI visibility	`ai_mentions`, `ai_visibility`, `ai_compare`, `ai_top_sources`, `ai_top_pages`, `ai_keyword_data`, `ai_llm_response`, `ai_scraper`, `ai_sample`, `ai_sample_status`, `ai_match`
Business data	`business_profile`, `profile_health`, `qa`, `business_listings`, `google_reviews`, `review_velocity`, `multi_platform_reviews`
Keyword research	`search_volume`, `keyword_overview`, `keyword_suggestions`, `related_keywords`, `keywords_for_site`, `keyword_trends`
Audits	`local_audit`, `citation_audit`, `reputation_audit`, `page_audit`
Competitive intel	`competitor_ads`, `brand_mentions`, `backlink_summary`, `backlink_gap`
Reports	`competitor_gap`, `local_authority`, `keyword_opportunities`
Geogrid	`geogrid_scan`, `geogrid_status`
Locations	`location_search`
Account / utility	`get_balance`, `history_search`, `history_get`, `ping`

AI visibility tools report on ChatGPT, Gemini, Perplexity, Claude and Google's AI Overviews and AI Mode. Each tool's description lists its credit cost, and the server sends your assistant instructions on which tool fits which question.

Example prompts

"Who ranks in the local pack for 'plumber' in Denver?"
"Run a full local SEO audit for Mike's Plumbing in Austin, TX"
"Compare my Google reviews to my top 3 competitors"
"Am I listed correctly on Apple Maps and Bing?"
"What keywords should a dentist in Portland be targeting?"
"Map my rankings on a 5x5 geogrid for 'bakery' in Brooklyn"
"How often does ChatGPT recommend my business for 'best pizza in Chicago'?"

Pricing

MCP calls use credits from your Local SEO Data account, the same as REST API calls. get_balance, location_search, ping, geogrid_status, ai_sample_status, history_search and history_get are free. See localseodata.com/pricing for plans, and check usage in your dashboard.

Running it yourself

HTTP server

The server listens on port 3003 by default (PORT changes it) and serves MCP at /mcp, with a health check at /health. Clients authenticate with ?key=YOUR_API_KEY or an Authorization: Bearer header. A Dockerfile is included.

Optional environment variables:

Variable	Default	Purpose
`API_BASE_URL`	`https://api.localseodata.com`	Local SEO Data API the tools call
`PORT`	`3003`	HTTP port
`OAUTH_ENABLED`	`false`	Advertise OAuth and accept OAuth access tokens
`OAUTH_ISSUER`	`https://localseodata.com`	Authorization server
`MCP_RESOURCE_URL`	`https://mcp.localseodata.com/mcp`	This server's public URL, used in OAuth metadata

OAuth access tokens are only accepted by the API from the hosted server, so a self-hosted copy should use API keys.

stdio

For clients that launch a local process:

Development

bash

npm run dev        # Watch modenpm run typecheck  # Type checknpm test           # Run testsnpm run build      # Compile to dist/

npm run dev        # Watch modenpm run typecheck  # Type checknpm test           # Run testsnpm run build      # Compile to dist/

License

MIT

Source: README.md at commit 5c26564

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.1.0LatestOct 15, 2026
v1.0.1Sep 16, 2026

Score

50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
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
License10 pts