# localseodata/mcp-server [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/localseodata/mcp-server  
**GitHub Stars:** 3  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/localseodata-mcp-server

## Description
42 local SEO tools for AI assistants. SERP tracking, Google Business Profile data, review monitoring, keyword research, citation audits, geogrid rank scans, AI visibility scoring, and competitive analysis. Install: npx @localseodata/mcp-server or connect to the hosted endpoint at mcp.localseodata.com.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-server": {
    "command": "npx",
    "args": ["-y","@localseodata/mcp-server"],
    "env": {
      "API_BASE_URL": ""
    }
  }
}
```

**Requires environment variables:** `API_BASE_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What localseodata/mcp-server MCP server does

The localseodata/mcp-server MCP server gives compatible AI assistants access to Local SEO Data through the Model Context Protocol. Its 42 tools cover local search results, Google Business Profile-related data, reviews, keywords, audits, competitor research, reports, geogrid scans, locations, and account utilities.

The service is designed for natural-language requests. After configuration, an assistant can select the relevant endpoint for questions such as which businesses appear in a local pack, which keywords a local business should target, or whether directory listings use consistent business information.

## How it works

The hosted deployment uses a streamable HTTP MCP endpoint at `https://mcp.localseodata.com/mcp`. Authentication is supplied as a `key` query parameter, so MCP clients do not need custom authorization-header configuration. API keys are created and revoked through the Local SEO Data dashboard.

The localseodata/mcp-server MCP server can also be built and run locally from the GitHub repository. The documented self-hosting flow installs Node.js dependencies, compiles the TypeScript project, and starts the compiled server. It listens on port 3003 by default, with `PORT` available to change that value. The documented backend setting is `API_BASE_URL`.

Requests consume credits from the associated Local SEO Data account. The README states that most endpoints cost one credit, listed as $0.005, and that usage can be monitored in the dashboard.

## Setup and configuration

Create an account, generate an API key, and place the key in the hosted endpoint URL. The same endpoint pattern is documented for Claude Desktop, Cursor, Cline, Windsurf, Claude Code, and VS Code with GitHub Copilot. Client configuration differs slightly: some clients use `url`, while Windsurf uses `serverUrl` and VS Code marks the connection as `streamable-http`.

For local deployment, clone the repository, run `npm install`, then `npm run build` and `npm start`. Set `API_BASE_URL=https://api.localseodata.com` before starting. A Dockerfile is included for container deployments.

## Tools and capabilities

The localseodata/mcp-server MCP server groups its tools into these areas:

- SERP and map research, including local packs, organic results, maps, local finders, and local services ads
- AI and LLM visibility, including overviews, mentions, comparisons, top sources, and top pages
- Business information, Google reviews, questions and answers, listings, and multi-platform reviews
- Keyword discovery, search volume, suggestions, site keywords, related terms, and trends
- Local, citation, reputation, page, and profile audits
- Competitor gaps, advertising research, brand mentions, and backlink analysis
- Review velocity, local authority, keyword opportunities, geogrid scans, location search, balance checks, and connectivity checks

## Limitations and notes

Access requires a Local SEO Data account and API key. Calls are metered against account credits rather than being an unmetered local data source. The hosted setup passes the credential in the URL, so client configuration should protect that endpoint value. The README documents MIT licensing and identifies port 3003 as the default for self-hosted operation.

_Full upstream README: https://allmcps.com/mcp/localseodata-mcp-server/readme_