Opencage Geocoding
Forward and reverse geocode addresses and coordinates worldwide from your agent while building maps, logistics, or location-aware features.
Overview
com.mcparmory/opencage-geocoding is a MCP server for the Build phase that converts addresses to coordinates and reverse-geocodes locations worldwide via OpenCage.
What is this MCP server?
- Convert street addresses to latitude/longitude worldwide via MCP tools
- Reverse-geocode coordinates back to human-readable locations
- stdio MCP server 1.0.2 via uvx (mcparmory-opencage-geocoding) or Docker
- Fits indie apps with store locators, delivery zones, or travel content
- Agent-callable geocoding without hand-rolling HTTP clients in every session
- Server version 1.0.2
- 2 package options: PyPI uvx and OCI Docker
- stdio MCP transport
Community signal: 25 GitHub stars.
What problem does it solve?
Manually calling geocoding APIs or guessing coordinates slows feature work when your agent could normalize addresses during implementation.
Who is it for?
Builders shipping location-aware SaaS, mobile, or API products who already use or plan OpenCage for geocoding.
Skip if: Products with no geo needs, or teams that require offline-only geocoding without external API calls.
What do I get? / Deliverables
Once configured, your agent can geocode and reverse-geocode on demand so location features get accurate coordinates inside the same build session.
- Forward geocoding results (address to coordinates) via agent tools
- Reverse geocoding results (coordinates to place descriptions)
- Reusable geocoding checks while implementing location-backed features
Recommended MCP Servers
Journey fit
Geocoding is a third-party API you wire in during Build when adding location fields, search, or map UX to your product. OpenCage is an external geocoding provider; integrations is the correct shelf for hooking address↔coordinate conversion into app logic or scripts.
How it compares
MCP geocoding API client, not a maps SDK skill or routing service.
Common Questions / FAQ
Who is com.mcparmory/opencage-geocoding for?
Solo developers integrating OpenCage who want agents to forward- and reverse-geocode while building location features.
When should I use com.mcparmory/opencage-geocoding?
Use it during Build integrations when you need address validation, coordinate lookup, or place names from lat/lng in app or script development.
How do I add com.mcparmory/opencage-geocoding to my agent?
Register stdio MCP with uvx mcparmory-opencage-geocoding 1.0.2 or ghcr.io/mcparmory/opencage-geocoding:1.0.2 and set your OpenCage API key in the server environment.