⬡ fencemaker
HomePricingUse CasesMigrate from RadarLive DemoQuickstartIntegrate with Android/iOS NEWPrompts for AI NEWMCP NEWDocsOperations Portal
Model Context Protocol

Fencemaker in your
AI coding assistant.

fencemaker-mcp gives Claude Code, Cursor, and Windsurf direct access to all 20 Fencemaker APIs. Your AI knows the exact endpoints, parameters, and response shapes — no more hallucinated Google Maps code.

Get API Key → API Docs →
⬡

Without MCP

Your AI defaults to Google Maps or Mapbox patterns — wrong endpoint paths, wrong auth headers, wrong response field names. You spend time correcting hallucinations.

→
⬡

With fencemaker-mcp

Your AI knows the real Fencemaker API surface. It generates working integration code on the first try — correct headers, correct endpoints, correct field names.

QUICK START

Zero setup. One command.

1

Get your API key

Generate a key at fencemaker.app/keys. It starts with gfnsr_live_.

2

Add to your editor config

~/.claude.json
{
  "mcpServers": {
    "fencemaker": {
      "command": "npx",
      "args": ["-y", "fencemaker-mcp"],
      "env": {
        "FENCEMAKER_API_KEY": "your_key_here"
      }
    }
  }
}
3

Start building

Restart your editor. Ask your AI to check if a coordinate is inside a delivery zone — it will call check_point with the correct Fencemaker API, no manual lookup needed.

20 TOOLS

Full Fencemaker API surface.

Every tool includes rich descriptions so your AI knows when and how to use each one.

Territories
list_territories List all geofence territories
get_territory Get territory details + GeoJSON boundary
create_territory Create a geofence from GeoJSON Polygon
update_territory Update name, code, color, active status, webhook
check_point Quick point-in-polygon check (lat/lon)
check_point_full Full territory lookup — supports address input
batch_check_points Check up to 1,000 points in one request
Devices & Tracking
register_device Pre-register a device with a label
list_devices List all tracked devices
get_device_status Current location + territories a device is inside
track_device Send GPS ping — triggers entry/exit webhooks
track_batch Batch GPS pings for up to 100 devices
Events & Webhooks
list_events Query entry/exit event history
simulate_event Trigger a test webhook event
webhook_health Delivery success rate + avg response time
Analytics
territory_overlaps Detect overlapping zones
api_usage API call stats by endpoint
Geocoding
geocode_address Address → coordinates
reverse_geocode Coordinates → address
autocomplete_address Real-time address suggestions

WEBHOOK PAYLOAD

What your server receives.

When a tracked device crosses a territory boundary, Fencemaker POSTs this JSON to your webhook URL. Your AI knows this shape exactly.

{
  "event": "entered",
  "device_id": "RIDER-042",
  "territory_id": "uuid",
  "territory_code": "ZONE-A",
  "territory_name": "South Bengaluru",
  "lat": 12.9716,
  "lon": 77.5946,
  "timestamp": "2026-05-30T10:45:00.000Z",
  "org_id": "your-org-uuid"
}

// Exit events also include:
"dwell_seconds": 342

Ready to add Fencemaker to your AI workflow?

Free tier included. No credit card required.

Get API Key → Read the Docs Sign Up Free