Overture Places vs Opencages
A side-by-side look at the Overture Places and Opencages MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Overture Places for location services work as a local process; choose Opencages for location services as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Overture Places when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Opencages when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_OPENCAGE_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 37/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | PLATFORM_OPENCAGE_KEY |
Tools & capabilities
Overture Places tools
No tool names declared yet. Check the project README from the listing page.
Opencages tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Overture Places
{
"mcpServers": {
"overture-places": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-overture-places"
]
}
}
}
Opencages
{
"mcpServers": {
"opencages": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-opencages"
],
"env": {
"PLATFORM_OPENCAGE_KEY": "YOUR_PLATFORM_OPENCAGE_KEY_HERE"
}
}
}
}
Frequently asked questions
Overture Places is categorized under Location Services and uses a local stdio subprocess. Opencages belongs to Location Services and uses a local stdio subprocess. Pick Overture Places for location services work and Opencages for location services.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Overture Places is listed as free. Auth: no auth required. Opencages has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add overture-places and opencages as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Overture Places has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Opencages has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
