Geocode.xyz MCP for AI. Turn addresses, text, or IPs into actionable data.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
Geocode.xyz converts physical addresses into precise latitude and longitude coordinates; it also reverses the process to find an address from GPS points.
This MCP extracts location names from messy text, checks where IP addresses originated, and suggests completions for better data entry.
What AI agents can do with Geocode.xyz Automation
Autocomplete
Provides suggestions for partial street names, postal codes, or city names as you type them.
Forward geocode
Converts a human-readable place name or address into precise geographic coordinates.
Geoparse
Scans long, messy blocks of text and extracts every location name it can identify.
It takes any readable address—a city, a landmark, or a street name—and spits out precise latitude and longitude numbers.
Give it coordinates, and it tells you the most likely physical mailing address associated with that point.
It scans unstructured documents or paragraphs and pulls out every location name it finds, regardless of how messy the text is.
You provide an IP address, and the tool returns its geographical origin, including the city and country.
When you type a partial street name or postal code, it offers accurate suggestions to keep your data clean.
Ask an AI about this
Waiting for input…
What AI agents can do with Geocode.xyz: Location Data Tools (5)
These five tools let you process all kinds of location data—from street names to IP addresses—and get actionable coordinates or physical addresses.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Geocode.xyz on VinkiusAutocomplete
Provides suggestions for partial street names, postal codes, or city names as you type them.
Forward Geocode
Converts a human-readable place name or address into precise geographic coordinates.
Geoparse
Scans long, messy blocks of text and extracts every location name it can identify.
Ip Geolocation
Looks up the geographical origin (city and country) associated with any provided IP...
Reverse Geocode
Converts a set of latitude and longitude coordinates back into a readable physical...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Geocode.xyz integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Geocode.xyz, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Geocode.xyz. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 5 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Dealing with messy addresses and locations in spreadsheets is a nightmare.
Today, you probably copy an address from one system into another. Then, if that address is missing coordinates or if the text description has multiple places mentioned, you end up running manual lookups on Google Maps or writing complex regex to pull out everything. It's tedious and slow.
With this MCP, your agent handles all of that mess. You give it a document full of random text, and instead of getting a vague response, you get clean lists of extracted locations. You don't copy anything; the data just appears ready to use.
Geocode.xyz gives you reliable coordinates from any source.
The biggest time sink is figuring out if a piece of text *is* an address, or if it's just mentioning a city name casually. Before this MCP, you had to build messy conditional logic: 'If the text has 5 words and contains a street type, then run X; otherwise, maybe run Y.'
Now, your agent routes the request correctly. Whether you pass in a written address using `forward_geocode` or just latitude/longitude coordinates for verification via `reverse_geocode`, you get clean results every time. The complexity vanishes.
What your AI can actually do with this
Need to work with locations but hate manually verifying every street name or cross-referencing maps? This connector gives your AI agent global geographic intelligence on demand. It handles five different kinds of location queries: converting a written address into coordinates, taking GPS points and finding the nearest physical place, automatically pulling out location names from huge chunks of text, determining where an IP address is located, and suggesting completions for partial entries.
When you connect Geocode.xyz through Vinkius, your AI client can query this data directly. You stop worrying about formatting or which API endpoint to hit. Instead, you just ask: 'What are the coordinates for that?' The system does the heavy lifting, giving you clean, verifiable spatial data instantly.
019e5d1f-5948-7075-bde1-c7482028e934 
Here's how it actually works
The bottom line is that you just ask for location intelligence, and your agent handles the complex API calls behind the scenes.
First, subscribe to this MCP and enter your Geocode.xyz API Key into the Vinkius platform.
Next, direct your AI client to perform a location query (e.g., 'What are the coordinates for...').
The system processes the request using the necessary geocoding method and returns precise coordinate data or verified addresses.
Who is this actually for?
Data Analysts who spend hours cleaning messy datasets. Logistics Managers needing to verify addresses for routing. Content teams that must tag locations mentioned in articles or posts.
Uses the MCP to enrich large spreadsheets by programmatically adding accurate coordinates and regional metadata to records based on text fields.
Checks if a client's stated address is valid or determines the best delivery point coordinates for route planning.
Processes articles and social media feeds to automatically identify and tag all mentioned locations before publishing.
What Changes When You Connect
Saves time on manual verification: Instead of manually checking every address in a spreadsheet against Google Maps, use forward_geocode to instantly get coordinates for thousands of entries.
Handles messy content: If you're pulling location mentions from customer feedback or articles, geoparse automatically extracts all the locations without you needing regex rules.
Improves data quality: When users are entering addresses into a form, use autocomplete to guide them and prevent simple spelling errors that break downstream processes.
Supports remote tracking: Need to know where an unknown IP address came from? Run ip_geolocation to get the city and country immediately for security or fraud checks.
Completes data sets: If you only have GPS coordinates (like from a tracker), use reverse_geocode to write out a clear, human-readable street address.
See it in action
Building a Delivery App
A logistics manager needs to verify if the customer's submitted ZIP code and street name are accurate. They ask their agent to run forward_geocode on the input, which returns the necessary coordinates for the routing API, ensuring the delivery truck knows exactly where to go.
Analyzing Customer Reviews
A content manager receives a large batch of unstructured customer reviews. They use geoparse to automatically pull out every location mentioned—'New York,' 'The coast,' 'near Miami'—allowing them to track regional popularity without reading the text.
Investigating Network Traffic
A security analyst intercepts a log file containing an unknown IP address. They run ip_geolocation on the IP, which immediately tells them it originated from Dublin, Ireland, narrowing down the investigation instantly.
Building User Forms
A web developer is building a multi-step form. Instead of letting users freely type an address, they integrate autocomplete to guide input, ensuring that when the user finally submits the data, it's clean and ready for forward_geocode.
The honest tradeoffs
Treating IP lookups as general geocoding
Assuming an IP address can be treated like a street name, and trying to pass it into forward_geocode.
For network data, you must use the dedicated ip_geolocation tool. This service handles the specific networking protocols needed to pinpoint location from an IP address, which is different from translating a written place name.
Copying and pasting addresses into text parsers
Pasting a list of structured addresses (e.g., '123 Main St, Anytown') into geoparse hoping it will find coordinates.
If you have a specific address or coordinate pair, use forward_geocode or reverse_geocode, respectively. Use geoparse only when the locations are embedded within paragraphs of descriptive text.
Over-relying on partial input
Assuming that just typing 'Paris' is enough, and running a geocoding query without specifying what kind of location it is.
To guarantee accuracy, use autocomplete first to get the fully qualified name (e.g., 'Paris, France'). Then pass that complete string to forward_geocode for coordinates.
When It Fits, When It Doesn't
Use this MCP if your core problem revolves around translating location data—whether that data is in a written format, a set of numbers (coordinates), or an IP address. You need the ability to go from A to B, and B back to A. Don't use it if you simply need to validate tax IDs, check zoning laws, or perform financial lookups; those require specialized industry APIs. If your goal is purely data manipulation without a geographic component, this tool won't help. However, if the input is location-related (text, address string, or IP), this suite covers almost every angle.
Questions you might have
How does geoparse work with long documents? +
It uses a specific POST method to handle large volumes of text, which means it won't fail on big articles or documents. It focuses solely on extracting location names from free-form writing.
Can I use forward_geocode if the address is incomplete? +
While it works best with full addresses, you can provide partial information and let the tool attempt to find the most likely match. However, for guaranteed accuracy, providing the complete name is always better.
What's the difference between ip_geolocation and forward_geocode? +
Forward geocoding takes a written street address (like '123 Main St'). IP geolocation takes an internet address (a string of numbers) and tells you where that connection point is.
Does autocomplete help with postal codes only? +
No. It helps with several things, including partial street names, city names, and postal codes. You can use it to improve accuracy across multiple data fields simultaneously.
What happens if I call `forward_geocode` with an address that doesn't exist? +
The MCP returns a specific error message indicating the location could not be found. This prevents your agent from treating bad data as valid coordinates, so you know exactly where the input failed.
If I call `reverse_geocode` with impossible latitude/longitude values, what result do I get? +
It returns an error status stating that the coordinates are outside known geographical boundaries. This is crucial for maintaining data integrity and ensuring your agent doesn't proceed with invalid points.
Does calling `geoparse` repeatedly in quick succession trigger rate limits, and how should I handle them? +
Yes, high-volume requests are subject to standard rate limiting. Your AI client must implement a retry mechanism with exponential backoff if it encounters a 429 status code.
When using `autocomplete`, are the suggestions limited only to street names, or can they include postal codes and cities? +
The tool suggests multiple location components. You'll receive structured results covering partial street names, city identifiers, and corresponding postal code options all in one call.
Can I extract multiple location names from a long paragraph of text? +
Yes! Use the geoparse tool. Provide the text in the scantext parameter, and the agent will identify and return all geographic locations mentioned within that text.
How do I find the address for a specific set of GPS coordinates? +
Use the reverse_geocode tool. Simply provide the lat (latitude) and long (longitude) values, and the server will return the closest physical address.
Is it possible to locate a user based on their IP address? +
Yes, the ip_geolocation tool allows you to input an IP address and retrieve the associated city, region, and country data.
We've already built the connector for Geocode.xyz. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 5 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.