The Local Falcon MCP server connects local SEO rank tracking to Claude, ChatGPT and any MCP-compatible agent. It exposes 37 tools for running geo-grid scans, reading rank reports, managing campaigns, monitoring Google Business Profiles and tracking visibility inside AI search engines. Sign-in is OAuth. Two of its tools spend metered credits, and grid size multiplies what they cost.
Anthropic states this reflects the level of review a connector received, not a security audit.
Local Falcon tools (37)
listLocalFalconScanReports
getLocalFalconReport
runLocalFalconScan
listLocalFalconCampaignReports
getLocalFalconCampaignReport
createLocalFalconCampaign
runLocalFalconCampaign
pauseLocalFalconCampaign
resumeLocalFalconCampaign
reactivateLocalFalconCampaign
listLocalFalconTrendReports
getLocalFalconTrendReport
listLocalFalconLocationReports
getLocalFalconLocationReport
listLocalFalconKeywordReports
getLocalFalconKeywordReport
getLocalFalconCompetitorReports
getLocalFalconCompetitorReport
listLocalFalconGuardReports
getLocalFalconGuardReport
addLocationsToFalconGuard
pauseFalconGuardProtection
resumeFalconGuardProtection
removeFalconGuardProtection
listLocalFalconReviewsAnalysisReports
getLocalFalconReviewsAnalysisReport
listAllLocalFalconLocations
getLocalFalconGoogleBusinessLocations
searchForLocalFalconBusinessLocation
saveLocalFalconBusinessLocationToAccount
getLocalFalconGrid
getLocalFalconRankingAtCoordinate
getLocalFalconKeywordAtCoordinate
listLocalFalconAutoScans
viewLocalFalconAccountInformation
searchLocalFalconKnowledgeBase
getLocalFalconKnowledgeBaseArticle
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
This connector spends money, and grid size sets the rate. One credit per grid point means a 15x15 scan costs 225 credits against a 3x3's 9. Enabling AI analysis adds 25 credits per report. Agree the grid size before you agree the scan.
No scan can be cancelled. Neither tool list contains a cancel, stop or refund tool, and the vendor's own instructions tell the calling model never to retry a submitted scan because the work is already queued. Pausing a campaign stops future scheduled runs, not one already in flight.
Auto-recharge removes the natural spending limit. Local Falcon recommends it as the fix for running out of credits, and it converts an empty balance from a hard stop into a purchase.
There is no read-only mode. The server and its authorization server both advertise one application scope, api. You cannot grant report reading without also granting scan running, so any read-only restriction has to come from your MCP client.
The vendor's pages disagree on the plan gate. One answer says the monthly Starter plan or higher; the requirements answer and Local Falcon's llms.txt both say Basic, because API access is included free with Basic and above. We report both. Verify against your own account.
Monthly credits expire monthly. Unused credits on a monthly package are gone at the end of the billing cycle. Annual plans hold them for the year.
The tool count is a floor, not a ceiling. The directory's 37 is a strict subset of the 39 the vendor's source registers, and the two extra names include a campaign-editing write. The vendor's own README and llms.txt also say 37.
We could not read live tool schemas or annotations. The endpoint requires authentication, so the names are the directory's and the annotation counts come from the published source at the version we pulled, not from the hosted deployment. We never authenticated, called a tool, or ran a scan or campaign.
A single scan report can overflow a context window. The vendor puts a typical report at 100–300KB and strongly recommends a field mask on every getLocalFalconReport call.
The endpoint rate-limits. Its responses carry a policy of 120 requests per 60-second window, observed on 2026-08-18.
Frequently asked questions
Does using the Local Falcon Claude Connector cost anything extra?
No extra charge for the connector itself, but scans still bill. Local Falcon's own answer states that initiating scans through Claude draws from your Local Falcon credits exactly as running them in the platform would, while pulling reports and other account lookups consume none. Ask the assistant to check your balance before starting a scan.
Does MCP cost extra?
No. Local Falcon's answer states you simply need to be on the monthly Starter plan or higher. Its Claude requirements answer and its own llms.txt both set the bar one tier higher at Basic, because API access is what the connector needs. Check your own plan before connecting rather than trusting either figure.
Can I run new scans through AI once MCP is connected?
Yes. Local Falcon states that once MCP is connected you can run new scans through AI tools without visiting your Local Falcon dashboard. That is the tool runLocalFalconScan, which the vendor marks destructive because it spends credits. Every grid point in the scan costs one credit and cannot be refunded.
What is a credit?
One credit is one data point on the geo-grid. Local Falcon defines a credit as a single map pin used during a scan, so a 5x5 grid scan uses 25 credits and a 9x9 uses 81. Grid size therefore multiplies cost quadratically, and a 15x15 scan costs 225 credits.
Can I control what data the AI tools can access through the MCP?
Only at the connection level. Local Falcon states both MCP options are permission-based and nothing is accessed without your authorization. The server advertises exactly one application scope, named api, so the consent screen grants the whole surface at once rather than letting you approve reads without writes.
What's the difference between Remote MCP and Local MCP?
Remote MCP is a cloud-hosted server managed by Local Falcon, which Local Falcon describes as fast, easy to set up and requiring no technical work. Local MCP is a self-hosted option that gives developers full control by running the MCP server on their own machine or infrastructure. This page documents the remote server.
Do Local Falcon credits expire?
Yes, on monthly plans. Local Falcon states that credits for monthly credit packages expire at the end of each month and credits for annual plans expire at the end of each year. Pay-as-you-go credits bought through auto-recharge never expire, which is what makes auto-recharge the setting to check before connecting an agent.
www.localfalcon.com/robots.txt — allows /answers/, carries no Content-Signal directive, and names both sitemap.xml and llms.txt (retrieved 2026-08-18) · retrieved 2026-08-18
Live auth posture check against https://mcp.localfalcon.com — anonymous initialize returned HTTP 401 on both the bare host and /mcp with an identical WWW-Authenticate: Bearer challenge carrying scope="api"; the resource descriptor, authorization-server metadata and OpenID configuration each returned HTTP 200 with api and offline_access (2026-08-18) · retrieved 2026-08-18
Sibling scope comparison — derived programmatically from the oauthScopes frontmatter of the 34 Agentman connector pages that record one, each probed on its own stated date
Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.
Use it in an agent
Put Local Falcon to work.
Connect Local Falcon once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.