EmbedEarth (E2) vs MCP Server
A side-by-side look at the EmbedEarth (E2) 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 EmbedEarth (E2) 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.
Which MCP server should you choose?
Choose EmbedEarth (E2) when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
Choose MCP Server when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You want tools like
uri.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 45/100 · Fair | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 361 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View EmbedEarth (E2) | View MCP Server |
Tools & capabilities
EmbedEarth (E2) 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.
EmbedEarth (E2)
{
"mcpServers": {
"embedearth-e2": {
"command": "npx",
"args": [
"-y",
"@embedearth/mcp"
]
}
}
}
MCP Server
{
"mcpServers": {
"mcp-server-139": {
"command": "npx",
"args": [
"-y",
"plop"
]
}
}
}
Frequently asked questions
EmbedEarth (E2) is categorized under Location Services and uses a local stdio subprocess. MCP Server belongs to Location Services and uses a local stdio subprocess. Pick EmbedEarth (E2) for location services work and MCP Server 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.
EmbedEarth (E2) has no declared pricing — check the project's own site. MCP Server 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 embedearth-e2 and mcp-server-139 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, EmbedEarth (E2) has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. MCP Server has 63/100 (Good) with 0 views, 0 installs and 361 GitHub stars.