Agents Index

EasyTerritory MCP

Online

Build, balance, realign and analyze sales/service territories; geocode, route, schedule, live map.

Visit publisherConnectJSON

What it can do: 58 tools

  • get_map_visualizationOpens the interactive territory map (Map Component) and returns map_url and map_session_id. Opens a blank map, or shows the latest state of an existing Territory Solution (e.g. yesterday's work) from ts_handle or a compl
  • get_guidance read-onlyReturns the EZT MCP operating guide: the cross-tool workflow order and shared rules (result.text, same text as the server instructions), result.server_version, and result.seat for the caller's key (plan standard|trial, k
  • discover_intent read-onlyMaps a free-text territory request to a workflow. Read-only keyword routing; no compute. Returns intent_category, the recommended tool order, the main tool (tier1_tool, null when the request is ambiguous) and alternative
  • workflow_advisor read-onlyReturns the next tool call for a multi-step workflow, given where the workflow stands. Read-only state machine; executes nothing. intent_category: build_from_accounts | account_grouping | known_assignments | realign_exis
  • ep_search read-onlySemantic search over the EZT MCP Expert Pack (EMEP): workflow guidance, concepts, interfaces, and common mistakes. Returns ranked markdown chunks with source files; atoms pulled in via `requires` are flagged requires_exp
  • ep_list_topics read-onlyLists EMEP topics grouped by type (concept, workflow, interface, troubleshooting, decision). Optional `type` filter.
  • ep_graph_traverse read-onlyTraverses the EMEP knowledge graph from a topic file (e.g. 'workflows/realign-by-selection.md') to related guidance, up to `depth` hops. Returns no edges unless the pack ships a _graph.yaml.
  • ensure_map_viewer read-onlyReports whether the person has the map open (viewer_status.connected) for a map_session_id from get_map_visualization, waiting up to wait_seconds (max 30 s per call; the result reports requested_wait_seconds and max_wait
  • submit_feedbackSends product feedback to EasyTerritory: a blocked or partial workflow, a workaround, a confusing response, or a missing capability. Returns an acknowledgement with feedback_id. Secrets, emails, Territory Solution JSON,
  • list_part_layers read-onlyReturns the available canonical part layers for territory construction (for example us_zips, us_counties, ca_fsa, and active country postal or administrative polygon layers), with the same metadata as ezt://part-layers:
  • query_parts read-onlyReturns attributes (no geometry) for parts of a part layer listed by list_part_layers or ezt://part-layers. Takes exactly one of filter (e.g. {state_abbr: TX}) or part_ids; neither or both returns INVALID_REQUEST. Paged
  • direct_buildBuilds territories from known part-to-territory assignments (a ZIP-to-territory sheet or file, including a three-level region/district/territory hierarchy via territory_path) and adds them to the Territory Solution as a
  • auto_buildPartitions ingested accounts into balanced sales territories with equal workload, metric, or count over a part layer (e.g. ZIPs) as a new alignment (TAL). User choices: build_mode (fixed_territory_count + territory_count
  • cluster_pointsGroups the points of one ingested layer into balanced clusters directly, with no ZIP or part layer and no territory alignment. Writes group_field (default group_id) on every point and colors the layer by it, replacing an
  • analyze_network_coverageFinds coverage gaps in a contractor (vendor, service provider, technician, repair shop) network: counts the contractors that reach each demand point (customer, claim, store, ZIP center). Reads contractor_layer (ingested
  • schedule_visitsSchedules recurring visits: expands each cadence (e.g. every 7 days) across a horizon and packs visits into daily buckets under a technician-day cap. Decides which day each visit happens (auto_build and cluster_points di
  • account_buildBuilds territories that follow an account column, such as rep name or territory code from CRM: each part goes to the group holding most of its accounts (conflict_policy). Adds a new alignment (TAL). Needs an ingested poi
  • realignMoves ZIPs or other parts (typed ids or ones selected on the map) from one territory into another within one alignment (tal_id): a ZIP move. moves=[{part_id, to_territory_id}], or realign_operation with part_ids. The Ter
  • delete_talDeletes one whole territory alignment (TAL: 'the territory layer', 'all territories') from the Territory Solution and the open map, in one synchronous call. Needs tal_id or the TAL's exact unique label, plus map_session_
  • delete_territoryDeletes one leaf territory from an alignment; its parts become unassigned. Needs tal_id, territory_id (the leaf id or its exact unique display name), and the Territory Solution from map_session_id or ts_handle. A territo
  • territory_splitTerritory split: divides one territory (e.g. an oversized one) into two while changing the rest of the alignment as little as possible (N to N+1 territories). Needs source_tal_id and target_territory_id, plus the Territo
  • territory_mergeMerges a pair of adjacent territories (N to N-1 territories). By default, territory_id_b is folded into territory_id_a (or renamed to new_territory_label) and the rest of the alignment rebalances with minimal disruption,
  • territory_rebalanceRebalances an existing alignment after the account data changed, keeping it as close to the current alignment as possible. Needs source_tal_id and the Territory Solution from map_session_id or ts_handle. point_layer defa
  • extract_tal_branchExtracts one regional branch of a hierarchical alignment (by branch_rollup_territory_id or branch_territory_path) into its own Territory Solution, so a delegate can edit just that region. Returns the extract plus branch_
  • reintegrate_branchMerges an edited branch (proposal Territory Solution from extract_tal_branch) back into the master. Needs branch_metadata and expected_master_revision; returns STALE_TS_REVISION when the master changed since the extract,
  • request_part_selectionLets the person adjust boundaries by picking parts (e.g. ZIPs) on the map: puts the open map into select mode on a part_layer, for purpose realign, a new territory, or a plain list. Returns selection_task_id; get_part_se
  • get_part_selection read-onlyReturns the state of a map selection task (selection_task_id from request_part_selection, or active_selection_task_id in ezt://map-sessions/{id}/state): status awaiting_user_selection, committed, expired, or cancelled, a
  • create_territory_from_partsCreates one leaf territory from a list of part_ids (e.g. a committed map selection), in a new alignment or an existing one (tal_id). With map_session_id the live map's Territory Solution is updated and repainted; otherwi
  • analyzeComputes territory statistics for one or more alignments, i.e. how balanced the territories are and how alignments compare: account counts, declared metric totals (e.g. Revenue), workload hours, balance scores, and cross
  • ingest_accountsAccount ingest: loads account rows (CRM records, a CSV, a spreadsheet) as point data on a named point layer of the Territory Solution, to add them to the map, geocoding rows without coordinates. Rows come only as account
  • request_account_uploadThe one way account or address rows enter the server: stages them for ingest_accounts (accounts_handle) or geocode_address (upload_handle) and returns upload_handle, csv_headers, and suggested_ingest args with a geocode_
  • request_assignment_uploadThe one way part-to-territory assignment rows (e.g. a ZIP-to-territory spreadsheet with Postal Code plus Territory/Region/Division) enter the server: stages them for direct_build (assignments_handle) and returns upload_h
  • geocode_addressGeocode-only pass: turns staged customer addresses into coordinates with match confidence, without loading a map layer. The rows are staged with request_account_upload (file, csv_text, or rows; up to 10,000 rows here) an
  • calculate_routeSequences and drives a set of stops, e.g. a technician from home to the depot, then the day's calls, and back home: returns the order, road distance, drive time, per-leg timings, and geometry from TomTom or Azure Maps, a
  • isochrone_buildDraws the area reachable by driving from one or more origins within a time or distance budget (drive-time area, service area, catchment) and adds each area as a territory in a drive-time alignment. origins: inline {latit
  • seed_buildGrows one territory outward from a seed {longitude, latitude} over a part layer until it holds a target: {type: location_count, value: N} or {type: metric_sum, field: <declared metric>, value: X}, counted from an ingeste
  • delete_routeRoute delete: removes one whole route from the Territory Solution and the open map, in one synchronous call. Needs route_id or the route's exact unique label, plus map_session_id or ts_handle. A route that is already gon
  • delete_point_layerPoint-layer delete: removes one point layer and its account points from the Territory Solution and the open map, in one synchronous call. Needs point_layer (the layer id or its exact unique label), plus map_session_id or
  • analyze_routes read-onlyReturns the total hours for each of the routes calculate_route has drawn: drive hours, dwell hours, route_workload_hours (provider drive time plus dwell, no visit-frequency multiplier), stop coordinates, centroid, and bb
  • points_in_territory read-onlyLists which account points from one point layer fall inside a territory polygon or a drive-time (isochrone) area. Per territory: point_count, metric_sums (metrics, else the layer's declared metric fields), and a sample o

…and 18 more.

Connect it

Claude Code
claude mcp add --transport http easyterritory-mcp https://mcp.easyterritory.ai/
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.easyterritory.ai/
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "easyterritory-mcp": {
      "url": "https://mcp.easyterritory.ai/"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "easyterritory-mcp": {
      "type": "http",
      "url": "https://mcp.easyterritory.ai/"
    }
  }
}

Questions

What does EasyTerritory MCP do?

Build, balance, realign and analyze sales/service territories; geocode, route, schedule, live map. It exposes 58 tools to AI assistants.

What tools does EasyTerritory MCP provide?

58 tools, including get_map_visualization, get_guidance, discover_intent, workflow_advisor, ep_search, ep_list_topics, ep_graph_traverse, ensure_map_viewer, submit_feedback, list_part_layers, query_parts, direct_build….

How do I connect EasyTerritory MCP to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.easyterritory.ai/ as a custom connector or MCP server. Copy-paste setup is on this page.

Does EasyTerritory MCP require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is EasyTerritory MCP online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes EasyTerritory MCP?

easyterritory.ai. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Travel, Maps & Places