Opencage Geocoding Mcp
Geocode and reverse-geocode addresses inside your agent via the OpenCage API without hand-rolling HTTP calls.
Overview
io.github.OpenCageData/opencage-geocoding-mcp is an MCP server for the Build phase that exposes OpenCage geocoding and reverse geocoding to your agent.
What is this MCP server?
- Official-style MCP server for the OpenCage geocoding API (npm @opencage/mcp-opencage-server v1.0.3)
- Stdio transport for local MCP hosts
- Requires YOUR_API_KEY env var (secret) per server.json
- Suits SaaS, mobile, and API products that need forward and reverse geocoding
- Keeps geolocation logic out of prompt spaghetti—agents call typed MCP tools
- Version 1.0.3 npm package @opencage/mcp-opencage-server
- 1 required environment variable YOUR_API_KEY
- Stdio transport; GitHub OpenCageData/opencage-geocoding-mcp
Community signal: 19 GitHub stars.
What problem does it solve?
Agents waste turns hand-writing geocoding HTTP requests and parsing OpenCage responses instead of shipping location features.
Who is it for?
Solo builders adding maps, search-by-location, or address validation who already have or will create an OpenCage API key.
Skip if: Workflow orchestration, OSINT investigations, or apps with zero geographic data needs.
What do I get? / Deliverables
Your MCP host gains OpenCage geocoding tools so address and coordinate lookups happen in one configured server with your API key.
- MCP tools backed by OpenCage forward and reverse geocoding
- Agent-ready location lookups without custom HTTP glue
- Production-aligned geo integration using your OpenCage quota
Recommended MCP Servers
Journey fit
Geocoding is integrated while building location-aware features, maps, or signup flows—not during passive idea research alone. Integrations subphase because the server wraps a third-party geocoding API for product code paths.
How it compares
Single-vendor geocoding MCP integration, not a multi-tool research or agent-bridge server.
Common Questions / FAQ
Who is io.github.OpenCageData/opencage-geocoding-mcp for?
Developers building location-aware products who want OpenCage accessible as MCP tools in their coding agent.
When should I use io.github.OpenCageData/opencage-geocoding-mcp?
Use it during Build integrations when implementing geocode, reverse geocode, or place search against OpenCage.
How do I add io.github.OpenCageData/opencage-geocoding-mcp to my agent?
Install @opencage/mcp-opencage-server, set YOUR_API_KEY in the MCP server env, add the stdio entry, and restart your client.