Geocoding vs Hindsight
A side-by-side look at the Geocoding and Hindsight MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Geocoding for location services work as a local process; choose Hindsight for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Geocoding when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You want tools like
geocode, reverse_geocode, search_places.
Choose Hindsight when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
HINDSIGHT_API_LLM_API_KEY, HINDSIGHT_API_LLM_PROVIDER, HINDSIGHT_DB_PASSWORD.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Knowledge & Memory |
| Quality signal | 59/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | HINDSIGHT_API_LLM_API_KEYHINDSIGHT_API_LLM_PROVIDERHINDSIGHT_DB_PASSWORD |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 53,323 |
| Directory activity | 4 views 0 installs 0 upvotes | 14 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Geocoding | View Hindsight |
Tools & capabilities
Geocoding tools 4
geocodeConvert an address, place name, or landmark into geographic coordinates. Use this tool when: - The user gives a place/address and you need its latitude/longitude - You need to disambiguate a place name (returns ranked matches) - You need a place's coordinates before another geo operation Args: query: Address, place name, or landmark. limit: Max results. country_codes: Optional ISO country filter. response_format: 'markdown' or 'json'. Returns: str: Ranked matches with coordinates, type, and full display name. Example: Input: {"query": "Eiffel Tower"} Output: 48.8584, 2.2945 — Tour Eiffel, Paris, Francereverse_geocodeConvert geographic coordinates into a human-readable address. Use this tool when: - The user gives latitude/longitude and wants to know what's there - You have coordinates (e.g. from geocode) and need the address Args: latitude: Latitude (-90 to 90). longitude: Longitude (-180 to 180). response_format: 'markdown' or 'json'. Returns: str: The address/place at those coordinates, with structured components. Example: Input: {"latitude": 48.8584, "longitude": 2.2945} Output: Avenue Anatole France, Paris, Francesearch_placesSearch for places or points of interest by description, with coordinates. Like geocode, but oriented toward finding multiple matching places/POIs (shops, landmarks, amenities) rather than resolving one address. Use this tool when: - The user wants places of a kind in an area ("parks in Austin") - The user wants options, not a single precise address Args: query: What to find, optionally including a location. limit: Max places. country_codes: Optional ISO country filter. response_format: 'markdown' or 'json'. Returns: str: Matching places with coordinates and type. Example: Input: {"query": "bookstores in Paris", "limit": 5} Output: Up to 5 bookstores with names and coordinatesdistance_betweenCompute the straight-line (great-circle) distance between two places. Geocodes both endpoints, then computes the as-the-crow-flies distance. (This is not driving/route distance.) Use this tool when: - The user asks how far apart two places are - You need a quick distance between two named locations Args: origin: Start place or address. destination: End place or address. unit: 'km' or 'miles'. response_format: 'markdown' or 'json'. Returns: str: The distance, plus the resolved coordinates of each endpoint. Example: Input: {"origin": "Paris", "destination": "Berlin"} Output: ~878 km between Paris and Berlin
Hindsight tools
No tool names declared yet. Check the project README from the listing page.
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.
Geocoding
{
"mcpServers": {
"geocoding": {
"command": "npx",
"args": [
"-y",
"geocode-mcp"
]
}
}
}
Hindsight
{
"mcpServers": {
"vectorize-io-hindsight": {
"command": "npx",
"args": [
"-y",
"@vectorize-io/hindsight-coding-agents"
],
"env": {
"HINDSIGHT_API_LLM_API_KEY": "YOUR_HINDSIGHT_API_LLM_API_KEY_HERE",
"HINDSIGHT_API_LLM_PROVIDER": "YOUR_HINDSIGHT_API_LLM_PROVIDER_HERE",
"HINDSIGHT_DB_PASSWORD": "YOUR_HINDSIGHT_DB_PASSWORD_HERE"
}
}
}
}
Frequently asked questions
Geocoding is categorized under Location Services and uses a local stdio subprocess. Hindsight belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Geocoding for location services work and Hindsight for knowledge & memory.
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.
Geocoding has no declared pricing — check the project's own site. Hindsight is listed as free. Auth: api key required. 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 geocoding and vectorize-io-hindsight as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Geocoding has a quality signal of 59/100 (Good) with 4 views, 0 installs and 1 GitHub stars. Hindsight has 57/100 (Good) with 14 views, 0 installs and 53,323 GitHub stars.