An MCP server that gives your assistant real business data
Nine tools an assistant can call directly: find businesses in a city, pull one full record, look up a company by its domain, read any public page as clean text, check whether an email can receive mail, check what a site allows crawlers to do, check a page's structured data, count matches for free, and read its own remaining credits. Hosted by us, so there is no package to install and nothing to keep updated.
POST/mcp
{
"mcpServers": {
"locomint": {
"type": "http",
"url": "https://api.locomint.io/mcp",
"headers": {
"Authorization": "Bearer ${LOCOMINT_API_KEY}"
}
}
}
}
What you get
Every field in the response.
| Field | Meaning |
|---|---|
local_search | Businesses for a category in a city, with a citation on each and text ready to quote |
count_local | How many match, before spending a credit. Free |
place_details | One full record: seven days of hours, contacts, technologies |
company_by_domain | What a company publishes about itself, from its domain name |
read_page | Any public page as markdown or text, with the contacts found on it |
verify_emails | Whether addresses can receive mail, without sending anything |
crawl_access | What a site allows AI crawlers to do, with the rule quoted |
check_schema | The structured data on a page, and the required fields it is missing |
account_usage | Credits used and left this month. Free |
How it works
What happens between your request and the response.
Hosted, not installed
A URL and your API key. No package on your machine, no version to upgrade, and new tools appear without you doing anything.
Your existing key
Send it as a bearer token. The same credits, quota and rate limit apply as on the REST API, and usage shows in the same dashboard.
Errors the model can act on
A wrong id or a spent quota comes back as a sentence, so the assistant corrects itself instead of failing the conversation.
The same rules
Public pages only, and a site that refuses automated visitors is left alone. Your agent inherits that position.
Pricing
One credit system for every endpoint.
Tools cost exactly what the matching endpoint costs: one credit per business, page, address or domain, free for counts and usage checks. Nothing extra for using the protocol.
The Google Maps MCP Server runs on the hosted API only, with a free key: 75 credits a month, 60 requests a minute, no card. There is no Apify listing for the protocol itself, and there does not need to be one: the section below shows how an assistant reaches the listings through Apify's own gateway.
Two ways to connect an assistant.
The hosted server above is one of them: our URL, your Locomint key, 75 credits a month on the free plan. The other is your own Apify account, where the same engine runs as thirteen pay-per-result listings. Apify's gateway offers any actor in its Store as a tool, so those listings are callable from an assistant with no Locomint key at all.
The hosted server
One URL and your API key, in the block at the top of this page. Every tool in the table above, 75 credits a month, 60 requests a minute, nothing to install and no version to keep up with. Start here to find out whether the tools do what you need.
Through your own Apify account
Point your client at Apify's gateway and name the Locomint listings in its tools parameter. Your assistant can then start a run and read the results, and Apify bills you per result at the listing's own price. This is the route for volume: a run sweeps a whole city on a grid rather than answering one request at a time.
{
"mcpServers": {
"apify": {
"type": "http",
"url": "https://mcp.apify.com/?tools=locomint/google-maps-scraper,locomint/google-maps-multi-city-scraper,locomint/google-maps-place-details-scraper,locomint/website-content-contact-extractor,locomint/website-crawler-content-contacts,locomint/bulk-email-verifier,locomint/company-enrichment,locomint/ai-crawler-checker,locomint/schema-markup-validator,locomint/career-site-jobs-scraper,locomint/tech-stack-detector,locomint/google-maps-email-extractor,locomint/google-ads-transparency-scraper"
}
}
}
The tools parameter is what selects them, so your assistant is offered these thirteen listings plus the few run-and-dataset tools Apify adds by itself so the results can be read back: calling one of these listings starts a run and hands back the id of its dataset, not the rows. Shorten the list to the listings you actually want. The first connection signs you in to Apify in a browser, which is why no token belongs in the file. A client that cannot do that sends an Apify API token as an Authorization: Bearer header instead.
A run costs what its listing costs, $0.50 to $10.00 per 1,000 results, charged by Apify to your account there rather than to us. Apify's own free plan includes $5 of usage a month with no card.
| Actor | What it runs | Price |
|---|---|---|
locomint/google-maps-scraper | Google Maps Scraper & Email Extractor | $3.00 per 1,000 places |
locomint/google-maps-multi-city-scraper | Google Maps Scraper | $3.00 per 1,000 leads |
locomint/google-maps-place-details-scraper | Google Maps Place Details Scraper | $2.50 per 1,000 records |
locomint/website-content-contact-extractor | Website Email Scraper | $1.50 per 1,000 pages |
locomint/website-crawler-content-contacts | Website Content Crawler | $1.50 per 1,000 pages |
locomint/bulk-email-verifier | Bulk Email Verifier & Validator | $0.90 per 1,000 addresses |
locomint/company-enrichment | Company Enrichment API | $5.00 per 1,000 domains |
locomint/ai-crawler-checker | AI Crawler Checker | $3.00 per 1,000 domains |
locomint/schema-markup-validator | Schema Markup Validator & Generator | $0.50 per 1,000 URLs |
locomint/career-site-jobs-scraper | Career Site Job Scraper | $6.00 per 1,000 jobs |
locomint/tech-stack-detector | Tech Stack Detector | $10.00 per 1,000 pages |
locomint/google-maps-email-extractor | Google Maps Email Extractor | $5.00 per 1,000 leads |
locomint/google-ads-transparency-scraper | Google Ads Transparency Scraper | $1.00 per 1,000 ads |
Questions
Things people ask about the Google Maps MCP Server.
Which assistants can use it?
Any client that supports remote Model Context Protocol servers over HTTP. In Claude Code it is one command; elsewhere it is a short block in a config file, both shown in the documentation.
Do I need a separate key or plan?
No. It is the same key, the same credits and the same dashboard as the REST API, and the free plan works.
What happens when my credits run out?
The tool answers with a plain message saying the monthly quota is spent, and the assistant relays it rather than inventing data. Nothing is charged for the refused call.
Can an assistant run the Apify listings instead?
Yes, and it needs no Locomint key to do it. Apify runs its own MCP gateway at mcp.apify.com and any actor in its Store can be loaded into it as a tool, so naming the Locomint listings in the gateway's tools parameter is the whole setup. Apify bills those runs per result at each listing's own price, and the config block is on this page.