Geo vs MCP Server
A side-by-side look at the Geo 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 Geo for location services work; choose MCP Server 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 MCP Server when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
uri.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | G Geo | |
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 37/100 · Fair | 64/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 363 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Geo | View MCP Server |
Tools & capabilities
Geo tools
No tool names declared yet. Check the project README from the listing page.
MCP Server tools 1
uriThe resource URI to read (e.g., `mapbox://categories`, `mapbox://categories/ja`)
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.
Geo
No confirmed install command for Geo yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCP Server
{
"mcpServers": {
"mcp-server-139": {
"command": "npx",
"args": [
"-y",
"@mapbox/mcp-server"
]
}
}
}