Opencellid vs Overture Places
A side-by-side look at the Opencellid and Overture Places MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Opencellid for location services work as a local process; choose Overture Places 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 Opencellid when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_OPENCELLID_KEY.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 41/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | PLATFORM_OPENCELLID_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Opencellid | View Overture Places |
Tools & capabilities
Opencellid tools
No tool names declared yet. Check the project README from the listing page.
Overture Places 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.
Opencellid
{
"mcpServers": {
"opencellid": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-opencellid"
],
"env": {
"PLATFORM_OPENCELLID_KEY": "YOUR_PLATFORM_OPENCELLID_KEY_HERE"
}
}
}
}
Overture Places
{
"mcpServers": {
"overture-places": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-overture-places"
]
}
}
}
Frequently asked questions
Opencellid is categorized under Location Services and uses a local stdio subprocess. Overture Places belongs to Location Services and uses a local stdio subprocess. Pick Opencellid for location services work and Overture Places 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.
Opencellid has no declared pricing — check the project's own site. Overture Places is listed as free. Auth: no auth required. 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 opencellid and overture-places as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Opencellid has a quality signal of 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Overture Places has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
