Data & Analytics · Opencage + Claude
Opencage MCP with Claude: Turn Addresses into Precise Location Data
The short answer
Claude works with Opencage through the Model Context Protocol (MCP), an open standard that acts as a secure adapter. Once connected with an API key, Claude can ask Opencage to convert addresses into coordinates, convert coordinates into addresses, and enrich lists of locations, all from a plain-English request.
What is Opencage?
Opencage is a geocoding service. It converts street addresses into latitude and longitude coordinates, and converts coordinates back into readable addresses. It draws on open location sources worldwide. Operations teams, logistics planners, developers, researchers, and customer-facing businesses use it to make location data accurate and usable inside their applications and reports.
How Claude connects to Opencage through MCP
The Model Context Protocol (MCP) is an open standard that lets Claude use other software securely. Think of it as a universal adapter between Claude and a tool. Through MCP, Claude can read information from Opencage and carry out defined actions, with permissions the organisation sets.
Once Opencage is connected, Claude can typically perform forward geocoding (address to coordinates), reverse geocoding (coordinates to address), and bulk lookups across a spreadsheet or list. Staff can describe what they need in ordinary language, and Claude carries out the lookups and returns structured results.
Access is controlled by the API key the organisation provides, which is scoped to the access it needs. Consequential actions, such as overwriting customer records, can be set to require a person's approval before they run. Every request can be logged, so the team can review what was done and when.
What you can automate
Cleaning customer address records
Operations teams often hold thousands of addresses with typos, missing postcodes or inconsistent formats. Claude can send these records to Opencage, flag addresses that could not be matched, and return standardised coordinates and formatted addresses for review before anything is saved back to the system.
Planning delivery and service routes
Field service and logistics managers can ask Claude to geocode a day's job list and group visits by area. Coordinates produced by Opencage give planners a reliable base for route tools, helping teams reduce wasted travel and plan appointments more realistically.
Enriching sales and market data
Sales and marketing teams can use Claude to add coordinates and regional detail to lead lists. This supports territory mapping, store catchment analysis and regional reporting, without staff copying data between tools by hand.
Verifying location details at onboarding
When customers or suppliers register an address, Claude can check it against Opencage and reverse-geocode a pin dropped on a map. Compliance and onboarding teams then see a clear match or a flagged exception to resolve.
Analysing location data for research
Researchers and analysts can convert field survey addresses into coordinates for mapping and analysis. Claude handles the repetitive lookups, so analysts spend their time interpreting results rather than formatting data.
An end-to-end workflow: Monthly branch address refresh
TriggerA branch manager uploads an updated list of branch addresses to the shared drive each month.
Claude reads the new address list and identifies rows with missing or unclear details.
Claude sends each address to Opencage for forward geocoding and records the coordinates and standardised format.
Addresses that do not match confidently are listed for a person to review.
Approved coordinates are written to the CRM branch records, with changes logged.
A summary of matched, flagged and updated records is posted to the operations team's channel in Microsoft 365.
OutcomeBranch records stay accurate and mappable each month, and the operations team spends less time on manual corrections. Typical results depend on the quality of the source data.
How we set it up
Free automation audit
We review your current address, mapping and location workflows and identify where Opencage and Claude would save the most time.
Secure API key connection
We set up the connection using the Opencage API key, with access limited to the geocoding functions your workflows require. The key is stored securely and can be rotated at any time.
Workflow design
We design the end-to-end process across Opencage and your other systems, such as Microsoft 365, your CRM or ERP, deciding which actions need human approval.
Testing with real cases
We test the workflow against past addresses and records, measuring match quality and checking edge cases before anything goes live.
Launch, monitoring and training
We launch with audit logs and monitoring in place, then train your team on how to run requests, review flagged results and escalate issues.
Who benefits
- Operations managers
- Cleaner address data and fewer manual corrections each month.
- Logistics and field service planners
- Reliable coordinates to support route and visit planning.
- Sales and marketing leads
- Location-enriched lead lists for territory and regional analysis.
- IT and data teams
- A governed, logged connection that fits existing security policies.
Security and control
- Access uses an API key scoped to the geocoding functions needed, following least-privilege principles.
- People approve any action that changes business records before it is saved.
- Audit logs record each request and change so results can be reviewed.
- Test runs on sample data confirm match quality before live use.
- Personal data is handled according to your policies and the data protection laws that apply to you.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can run this workflow with hosting and data handling that meet their own compliance requirements. In India, we align the setup with the Digital Personal Data Protection Act, 2023. For organisations in the UAE and Saudi Arabia, we follow the applicable local data protection laws. Custom applications can be hosted in India, the United States, the United Kingdom or the European Union, chosen to meet your requirements.
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 Opencage MCP server do?
The Opencage MCP server gives Claude a secure way to use Opencage's geocoding functions. It lets Claude convert addresses into coordinates, convert coordinates into addresses, and run bulk lookups, following the permissions you set. It acts as the adapter between Claude and Opencage, so requests can be made in plain language.
Is connecting Opencage to Claude secure?
Security depends on how the connection is configured. We use an API key scoped to the functions your workflow needs, store it securely, and log requests. Actions that change records can require human approval. We design the setup around your security policies before launch.
What can Claude do with Opencage once connected?
Typically, Claude can geocode single addresses, reverse-geocode coordinates, process lists of addresses in bulk, and add location detail to your existing data. It can also summarise results and flag addresses that did not match, so your team can review them.
How long does setup take?
Timelines depend on the number of workflows and the state of your data. A focused setup for one geocoding workflow is often completed within a few weeks, including testing and team training. We confirm the timeline after the free automation audit.
What access or plan do I need?
You need an Opencage account that issues an API key for the geocoding functions you plan to use. The suitable level of access and usage depends on your request volumes, so we review your needs during the audit and confirm what your account requires.