Claude Code

Sign in with your account

claude mcp add --transport http localseodata https://mcp.localseodata.com/mcp --scope user

Then run /mcp inside Claude Code, pick localseodata and follow the browser sign-in. From a shell you can run claude mcp login localseodata instead; add --no-browser over SSH and paste the redirect URL back.

--scope user makes it available in every project. Leave it off to add it to the current project only.

Using an API key instead

claude mcp add --transport http localseodata https://mcp.localseodata.com/mcp --scope user --header "Authorization: Bearer YOUR_API_KEY"

With a header set, Claude Code doesn't fall back to sign-in. You'll find your API key in the API Keys dashboard. It starts with sk_live_.

Sharing it with a team in .mcp.json

{
  "mcpServers": {
    "localseodata": {
      "type": "http",
      "url": "https://mcp.localseodata.com/mcp",
      "headers": { "Authorization": "Bearer ${LSD_API_KEY}" }
    }
  }
}

Each person sets LSD_API_KEY in their own environment. Keep "type": "http": an entry without it is read as a local command and skipped.

Check it works

Ask: "What's my Local SEO Data balance?" That calls the free get_balance tool, so it costs nothing and shows the connection is live. Then try a real question, like "Who are the top 3 on Google Maps for plumbers in Denver?" Most answers cost 2 to 10 credits, and new accounts start with 100.