Gods Eye Geospatial Mcp vs Directory

In-depth architectural comparison of the Gods Eye Geospatial Mcp and Directory 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.

Which MCP Server Should You Choose?

G

Choose Gods Eye Geospatial Mcp when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Gods Eye Geospatial Mcp Details

Choose Directory when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Directory Details

Feature & Specification Comparison

Specification	G Gods Eye Geospatial Mcp Developer Tools	Directory Developer Tools
Summary	Gods Eye — civilian open-source geospatial awareness MCP. Wraps open-licence APIs (ESA Coper...	Discover and query every business on ANOTS — search, ask, or find-and-ask over MCP.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "gods-eye-geospatial-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli@latest"
      ]
    }
  }
}

{
  "mcpServers": {
    "directory": {
      "url": "http://localhost:6333/health"
    }
  }
}

Related MCP Server Comparisons