In-depth architectural comparison of the NUM and Emem MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
NUM
Location Services · Remote HTTP/SSE
Quality: 36/100 (Fair) | Auth: No auth required
Emem
Location Services · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose NUM if you need specialized Location Services tools running via a hosted cloud SSE transport. Choose Emem if your workspace requires Location Services integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose NUM when:
You need dedicated capabilities in the Location Services domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Real places for your agent. Search 2.5M+ travel places; submit a business for human review.
Earth memory MCP server that gives AI agents signed geospatial facts and cite-able receipts for place-based questions. Covers elevation, land cover, surface water, vegetation, and built-up context. Public endpoint at https://emem.dev/mcp.
NUM is categorized under Location Services and uses a remote streaming HTTP/SSE transport. In contrast, Emem belongs to Location Services using local stdio subprocess. Select NUM when you need capabilities focused on location services and Emem when you require tools for location services.