@shyzus/mcp-geocrafter 1.5.1 → 1.5.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +6 -6
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -34,9 +34,9 @@ This application allows **ChatGPT** and other MCP clients to access geocoding se
34
34
 
35
35
  ### ✨ Features
36
36
 
37
- - 🔍 **Address to GPS** - Convert addresses to coordinates with multi-provider support
38
- - 📍 **GPS to Address** - Convert coordinates to addresses
39
- - 🔄 **Multi-Provider** - Google Geocoding API + Photon API (OpenStreetMap), selectable per request
37
+ - 🔍 **Address to GPS** - `search_address_google` (recommended) + `search_address_photon` (fuzzy matching)
38
+ - 📍 **GPS to Address** - `reverse_geocode_google` (recommended) + `reverse_geocode_photon`
39
+ - 🔄 **Multi-Provider** - Dedicated tools per provider the LLM picks the right one automatically
40
40
  - 🔗 **Geohash Encoding/Decoding** - Convert coordinates to geohash strings for location deduplication
41
41
  - 📏 **Distance Calculation** - Haversine formula to compute exact distance between two GPS points
42
42
  - 🏗️ **Modular Architecture** - Clean separation of concerns, reusable for future MCP servers
@@ -50,7 +50,7 @@ This application allows **ChatGPT** and other MCP clients to access geocoding se
50
50
  | **Google** (recommended) | POIs, businesses, intent-based queries ("gare ales france") | Requires API key, 10k free/month |
51
51
  | **Photon** | Typo-tolerant search on place/street names, no API key needed | Less accurate on POI resolution |
52
52
 
53
- The LLM automatically picks the best provider based on query type, or the user can force one (e.g. "use Google", "use Photon").
53
+ Each provider has its own dedicated tools — the LLM sees both options and picks the right one. Users can also force a provider (e.g. "use Google", "use Photon").
54
54
 
55
55
  ### 💬 Usage examples
56
56
 
@@ -524,8 +524,8 @@ CORS_ORIGIN=* # CORS origin (default: * in dev, https://cha
524
524
  - **Server-side**: Set `GOOGLE_API_KEY` environment variable — all clients benefit automatically
525
525
  - **Per-request**: Pass `apiKey` parameter in the tool call — for N8N, automations, or when you don't control the server
526
526
  - **Photon**: Always available, no configuration needed. You can optionally self-host (set `PHOTON_BASE_URL`).
527
- - The `provider` parameter on `search_address` and `reverse_geocode` tools lets the LLM override the default per request.
528
- - The `apiKey` parameter is never logged, never stored, never returned in responses.
527
+ - Each provider has **dedicated tools** (`search_address_google`, `search_address_photon`, etc.) no `provider` parameter needed.
528
+ - The `apiKey` parameter on Google tools is never logged, never stored, never returned in responses.
529
529
 
530
530
  ---
531
531
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@shyzus/mcp-geocrafter",
3
- "version": "1.5.1",
3
+ "version": "1.5.3",
4
4
  "description": "GeoCrafter - MCP server for geocoding, reverse geocoding, geohash and distance calculation - Powered by Photon API",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",