Data & Analytics · Geokeo + Claude
Geokeo MCP with Claude: Turn Addresses into Verified Map Coordinates
The short answer
Claude works with Geokeo through the Model Context Protocol, a secure standard that lets Claude use other software with permissions you control. Once connected with an API key, Claude can convert addresses into coordinates, turn coordinates back into addresses, check locations and process large lists of places, all from a plain English request.
What is Geokeo?
Geokeo is a geocoding service. It converts street addresses into latitude and longitude coordinates, and converts coordinates back into readable addresses. Businesses use it to place customers, branches, deliveries and assets on a map, and to check that addresses are real and correctly formatted. It offers a generous free tier, which suits small teams and early-stage projects that need fast, accurate location lookups.
How Claude connects to Geokeo through MCP
The Model Context Protocol, or MCP, is an open standard that acts like a universal adapter between Claude and other business software. It lets Claude read information from a tool and take actions in it, while the organisation decides exactly what is allowed. Geokeo can be connected to Claude through its API key, using a secure connector set up by our team.
Once connected, Claude can typically send address lists to Geokeo for conversion, ask for the address behind a set of coordinates, check whether a location is valid, and run batches of records in one go. You simply describe the task in everyday language, such as asking Claude to find coordinates for every branch in a spreadsheet and flag any address that cannot be found.
Permissions and approvals keep people in charge. Access is limited to the minimum needed, the API key is stored securely and can be rotated at any time, and consequential actions such as overwriting a customer master file can require a person to approve them first. Every request is logged so the team can review what was done and when.
What you can automate
Cleaning customer address databases
Operations teams often hold thousands of addresses with typos, missing postcodes or inconsistent formats. Claude can send these records to Geokeo, standardise the results and flag entries that cannot be matched, so the team reviews only the exceptions instead of checking every row by hand.
Mapping branches and service areas
A retail or services business can ask Claude to convert a list of store or office addresses into coordinates, then group them by region. Sales and operations leaders get a clear picture of where they are present and where coverage gaps exist, without waiting for an analyst to prepare the data.
Validating delivery and pickup locations
Logistics and field service coordinators can have Claude check job addresses before dispatch. Invalid or ambiguous locations are caught early, reducing failed deliveries and wasted journeys. Claude can summarise the problem addresses so dispatchers know what to correct first.
Reverse geocoding GPS data from field teams
When field staff or equipment report only coordinates, Claude can use Geokeo to turn those points into readable street addresses. Managers get reports they can understand at a glance, such as which site an inspection took place at, without needing a mapping specialist.
Preparing location data for analysis
Analysts preparing reports on sales, incidents or customer density often need clean coordinates before they can build maps or models. Claude can batch process the data, add coordinates to each record and hand back a file ready for the reporting tool the team already uses.
An end-to-end workflow: New customer onboarding and territory assignment
TriggerA new customer record is created in the organisation's CRM with a postal address.
Claude reads the new customer address from the CRM record.
Claude sends the address to Geokeo to convert it into coordinates and confirm it is valid.
If the address cannot be matched, Claude flags the record and asks a team member to correct it.
Claude matches the coordinates to the correct sales territory defined in the organisation's rules.
The coordinates and territory are written back to the CRM, and the account owner is notified in Microsoft Teams.
The activity is logged in the audit trail for review.
OutcomeCustomers are placed on the map correctly from day one, sales territories are assigned without manual lookup, and fewer records are left with incomplete location data.
How we set it up
Free automation audit
We review your current address handling, mapping and location workflows to find where Geokeo and Claude will save the most time. You receive a clear list of priorities at no cost.
Secure connection with an API key
We set up the Geokeo connection using your API key, stored securely with access limited to the minimum required. The key can be rotated at any time without disrupting other systems.
Workflow design
We design the end-to-end process across Geokeo and your other systems, such as your CRM, spreadsheets or Microsoft 365. People approve any action that changes important records.
Testing with real past cases
We test the workflow against real addresses from your own history, measure accuracy and tune the validation rules so that exceptions are caught reliably.
Launch, monitoring and training
We launch with audit logs and monitoring in place, then train your team on how to make requests, review flagged records and handle exceptions.
Who benefits
- Operations managers
- Cleaner address data and fewer failed deliveries or missed visits.
- Sales and territory leaders
- Accurate maps of customers and branches for planning and coverage decisions.
- IT and data teams
- A secure, monitored connection that reduces manual data cleaning work.
- Field service and logistics coordinators
- Early warnings about invalid locations before jobs are dispatched.
Security and control
- The API key is stored securely, access is limited to the minimum needed, and the key can be rotated at any time.
- Actions that change important records require approval from a named person.
- Every request and change is recorded in an audit log that your team can review.
- Results are checked against defined validation rules, and uncertain matches are flagged rather than silently accepted.
- Address data is handled only as needed for the task and is governed by your existing data policies.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host their Claude automations in the United States, the United Kingdom or the European Union, depending on their data requirements. Businesses in India must meet the Digital Personal Data Protection Act, 2023, and can host in India. Organisations in the UAE and Saudi Arabia must follow local data protection laws, and we select the hosting region to meet those requirements before any workflow goes live.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Geokeo MCP server do?
The Geokeo MCP server acts as a secure bridge between Claude and Geokeo's geocoding service. It allows Claude to send addresses for conversion into coordinates, send coordinates for conversion into addresses, and check locations, all through natural language requests. You keep control of what the connection can do.
Is connecting Geokeo to Claude secure?
The connection uses an API key, which we store securely and limit to the actions your workflow needs. Access can be changed or revoked at any time. Consequential actions can require human approval, and every request is logged so your team can review activity.
What can Claude do with Geokeo once it is connected?
Claude can typically convert single addresses or large lists into coordinates, perform reverse geocoding on GPS points, validate whether locations exist, and batch process records. It can also summarise results and pass cleaned data to your other business systems.
How long does setup take?
Setup time depends on how many systems are involved and how complex your rules are. A focused address validation workflow is often ready within a few weeks, including testing with your own data and staff training. We confirm a timeline during the free automation audit.
Which plan or permissions do I need?
Generally, you need a Geokeo account that issues an API key for your organisation. Your usage limits depend on the plan you hold, and the free tier can be enough for smaller volumes. During the audit we review your expected request volumes and access needs so the setup matches your account.