← Directory
mcp · Global
opencage-geocoding-mcp
MCP server for querying the OpenCage geocoding API from within LLMs
Claim this listing
Represent opencage-geocoding-mcp? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.
What's in it
- Data offered docs-verified
- forward geocoding (address or place name to lat/long) · reverse geocoding (coordinates to address) · API usage and rate-limit status
- Coverage llm-inferred
- Global
- Formats llm-inferred
- MCP stdio
- Access docs-verified
- API key required (OPENCAGE_API_KEY) from OpenCage, which offers a free-trial key; MCP server licence MIT
Useful for
- Use cases llm-inferred
- Convert site addresses to coordinates for a desk-based constraints screen · Reverse-geocode survey or monitoring point coordinates to nearest address or locality for report labelling · Quick place-name lookup to confirm the county or district of a study area during scoping
- Audience llm-inferred
- GIS analysts · environmental consultants · civils engineers · planners
Limitations
- Constraints llm-inferred
- Designed for small volumes of geocoding; bulk CSV or database work is better served by OpenCage CLI tools or direct API calls · Requires Node.js 20 or higher and a local clone, npm install and build · Desktop config needs an absolute path to the built server file · Setup examples target the claude.ai desktop client; other MCP clients may need different configuration · Rate limits apply to accounts with hard limits; subscription accounts have no hard usage limits · First use requires the user to grant permission in the client
Example tool calls docs-verified
Get coordinates and location details for a site or place name, restricted to the UK
{
"tool": "geocode-forward",
"arguments": {
"query": "Trafalgar Square, London",
"countrycode": "gb",
"limit": 1
}
}Convert survey or monitoring point coordinates to an address for labelling
{
"tool": "geocode-reverse",
"arguments": {
"latitude": 51.508,
"longitude": -0.1281
}
}Check remaining API requests and rate-limit reset times before a batch of lookups
{
"tool": "get-opencage-info",
"arguments": {}
}- Licence
- MIT
- Authentication
- Credentials via env: OPENCAGE_API_KEY (README-verified)
- GitHub stars
- 19
- Last commit
- 29/09/2026
- Last successful page check
- 14/10/2026
- Page health
- healthy
- Package
- Not recorded
- Verification
- Not independently verified
Provenance & evidence
Tools/install/auth auto-extracted from README; quality score heuristic (stars, recency, tool count, licence).
Metadata observed 15/10/2026 · research sweep: github-search