MCP server for querying the OpenCage geocoding API from within LLMs
Last commit November 1, 2026, 11 days ago.
19 GitHub stars and 0 Honeystax upvotes. Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
Starts at 6. Added: GitHub health 37/100 +22, no security policy +8, no contributing guide +4, no code of conduct +3.
AI Agent
Universal
Model
Multiple
Fastest way to find out if opencage-geocoding-mcp belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add opencage-geocoding-mcp -- npx opencage-geocoding-mcpRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove opencage-geocoding-mcpNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ opencage-geocoding-mcp ← registers here
opencage-geocoding-mcp is listed on Honeystax as a MCP Server for Universal, since June 20, 2026. Its code is at github.com/OpenCageData/opencage-geocoding-mcp, with 19 GitHub stars and 0 open issues. Last commit November 1, 2026, 11 days ago. GitHub's community health check gives it 37 out of 100.
Source: GitHub repository
Source check: November 1, 2026
Upstream commit: November 1, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.