How to Use the Pelias Geocoder MCP in Claude
Get real-world coordinates and clean addresses using this MCP Server directly in your Claude Desktop chat.
Works with every AI agent you already use
…and any MCP-compatible client
Connect Pelias Geocoder MCP to Claude Desktop
Create your Vinkius account to connect Pelias Geocoder to Claude Desktop — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.
Key Capabilities
Real-time address lookups inside Claude Desktop
Stop copying addresses out of your Claude Desktop chat to search them on a separate map. When you feed your agent raw location text, it fires up `search_geocode` to return precise latitude and longitude coordinates. If you have clean, segmented data fields like region or postal code, the `structured_geocoding` tool ensures you bypass parsing guesswork entirely. Your local desktop app runs these queries as background subprocesses, pulling exact GIS coordinates into your prompt context. You can immediately use the resulting coordinates to map out branch locations or clean up customer shipping tables on the fly.
Map visual boundaries directly from your chat window
You can limit what Claude Desktop sees by setting geographic limits. Tell your agent to search for points of interest only within a specific map view, and it uses `search_bounding_box` to restrict the API requests to those exact coordinate bounds. If you need political boundaries, the `search_country_filter` tool limits matching to ISO 3166 country rules. Running this MCP Server locally via your config file means your coordinate limits stay fast and direct. Your agent filters out global noise and focuses only on the neighborhoods or countries you actually care about.
Reverse geocode coordinates using local tools
Drop a set of raw coordinates or a GPS trace into Claude Desktop to find out what is actually there. Your agent calls `reverse_geocode` to convert those numbers back into real OpenStreetMap address pins. You can tighten the search radius by letting the agent trigger `reverse_distance_limit` so it does not return matches miles away. This local MCP setup handles the heavy spatial matching directly on your machine. You get the exact street names, postal codes, and neighborhood names without manual API testing.
Set up Pelias Geocoder MCP in Claude Web or Desktop
- 1
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
- 2
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcpReplace[YOUR_TOKEN_HERE]with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials. - 3
Start a conversation
Open a new chat. The Pelias Geocoder MCP tools are available immediately — no restart needed.
Endpoint URL
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp No configuration file needed — paste the URL directly in the Claude web interface.
Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.
Why Choose Vinkius
Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.
Real-time monitoring
Live
visibility into every interaction
Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.
Built-in savings
60%
lower AI costs
Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.
Single dashboard
One
place for every integration
Every tool your AI connects to, managed from a single screen. One account, complete control.
Common questions about Pelias Geocoder MCP in Claude Desktop
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
Start using the Pelias Geocoder MCP today
We host it, we monitor it, we maintain it. You just paste one token.