A side-by-side look at the Overture Places and MCP Server 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 MCP Server for location services as a local process. You can also run both side by side in one mcpServers block.
uri.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 37/100 · Fair | 63/100 · Good |
| 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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 361 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Overture Places | View MCP Server |
No tool names declared yet. Check the project README from the listing page.
uriThe resource URI to read (e.g., `mapbox://categories`, `mapbox://categories/ja`)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.
{
"mcpServers": {
"overture-places": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-overture-places"
]
}
}
}
{
"mcpServers": {
"mcp-server-139": {
"command": "npx",
"args": [
"-y",
"plop"
]
}
}
}