EasyTerritory is an MCP server with 58 tools an agent can call, among them account_build, analyze, analyze_network_coverage. It answers at https://mcp.easyterritory.ai/ over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 29 September 2026; the last check, on 15 November 2026, succeeded.
Build, balance, realign and analyze sales/service territories; geocode, route, schedule, live map.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
account_build | Builds 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 point_layer, grouping_f Inputs: point_layer, grouping_field, part_layer, tal_label, ts_handle, expected_revision |
analyze | Computes 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-TAL comparison; hyp Inputs: ts_handle, job_id, tal_ids, part_layer, metrics, scope |
analyze_network_coverage | Finds 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 with layer_role=cont Inputs: contractor_layer, demand_layer, coverage, trade, contractor_filter, demand_metric |
analyze_routes | Returns 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 bbox. Synchronous. Nee Inputs: route_ids, map_session_id, ts_handle, dwell_time |
auto_build | Partitions 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, fixed_workload_tar |
calculate_route | Sequences 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, and draws the path wi |
cluster_points | Groups 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 any prior color classi Inputs: point_layer, build_mode, ts_handle, expected_revision, objective, dwell_time |
configure_map | Updates map settings on the Territory Solution and refreshes the live map: project_name (map heading), theme (dark | light basemap and UI style), loaded_part_layers ([] hides ZIP/part outlines; builds never load them), active_part_layer, ac |
create_territory_from_parts | Creates 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; otherwise ts_handle (a new Inputs: part_layer, part_ids, territory_name, territory_path, tal_id, conflict_policy |
delete_point_layer | Point-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 ts_handle. Territor Inputs: point_layer, map_session_id, ts_handle |
delete_route | Route 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 gone returns ok with al Inputs: route_id, map_session_id, ts_handle |
delete_tal | Deletes 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_id or ts_handle. Poi Inputs: tal_id, map_session_id, ts_handle |
delete_territory | Deletes 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 territory that is already g Inputs: tal_id, territory_id, ts_handle, part_layer, expected_revision, repair_policy |
direct_build | Builds 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 new alignment (TAL). Inputs: part_layer, tal_label, assignments_handle, ts_handle, tal_id, expected_revision |
discover_intent | Maps 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 alternatives, required_inputs, Inputs: user_request, context |
ensure_map_viewer | Reports 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_seconds). Works the Inputs: map_session_id, wait_seconds, poll_interval_ms |
ep_graph_traverse | Traverses 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. Inputs: file_path, depth, edge_kinds |
ep_list_topics | Lists EMEP topics grouped by type (concept, workflow, interface, troubleshooting, decision). Optional `type` filter. Inputs: type |
ep_search | Semantic 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_expanded. Degrades to t Inputs: query, type, tags, max_results |
export_geojson | Exports the territory solution as one GeoJSON file to share, archive, or open in EasyTerritory Designer: territory polygons with part_ids, points, and routes with numbered stops, each carrying its displayed style. tal_ids, point_layers, and Inputs: ts_handle, job_id, map_session_id, tal_ids, point_layers, route_layers |
extract_tal_branch | Extracts 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_metadata, which rein Inputs: tal_id, branch_rollup_territory_id, branch_territory_path, ts_handle, expected_revision, expected_content_hash |
ezt | Plain-language orchestrator: takes request (the goal) and runs the matching workflow in one call, optionally with csv_file (a host file parameter), accounts_handle, assignments_handle, map_session_id, or ts_handle. An uploaded CSV is parsed Inputs: request, state_facts, args, csv_file, accounts_handle, assignments_handle |
geocode_address | Geocode-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) and passed as its uplo Inputs: upload_handle, country_hint, region_hint, min_confidence, force_regeocode, use_cache |
get_guidance | Returns 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, key_expires_at, and q |
get_map_selection | Returns the most recent committed selection on an open map session (map_session_id): part_layer, part_ids, and selection_task_id when the selection came from request_part_selection. Covers selections the person started from the map legend. Inputs: map_session_id |
get_map_visualization | Opens 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 completed job_id. Idempot Inputs: mode, active_tal_id, theme, presentation, expiry_seconds, interaction_flags |
get_part_selection | Returns 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, and once committed th Inputs: selection_task_id |
import_dataverse_view | Microsoft Copilot only (Entra sign-in): reads a Dynamics 365 account view server to server, as the signed-in user, and stages it as an account upload. No rows pass through the agent. view_id (or an exact view_name) comes from list_dataverse Inputs: environment_url, view_id, view_name, point_layer, map_session_id |
import_designer_project | Opens an EasyTerritory Designer project as a Territory Solution: the server exports it from Designer and imports it (part-based territories, non-part polygon areas such as radius buffers or hand-drawn shapes, point layers up to 200,000 poin Inputs: project_id, include_points, point_layers, include_routes, include_manual_polygons, part_layer |
import_geojson | Opens a GeoJSON FeatureCollection (points, or a territory file, plain or gzip/zip) as a Territory Solution; returns ts_handle and a summary. A file of any real size moves by reference, never inline: call with no file argument for an upload_ Inputs: geojson, geojson_text, geojson_gzip, geojson_file, upload_handle, point_layer |
ingest_accounts | Account 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 accounts_handle from reques Inputs: accounts_handle, point_layer, label, label_field, latitude_field, longitude_field |
isochrone_build | Draws 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 {latitude, longitude} or a Inputs: origins, bands, travel_mode, route_type, traffic, depart_at |
link_designer | Connects the customer's EasyTerritory Designer account so list_designer_projects, import_designer_project, and push_to_designer can call Designer from the server. Returns status linked (designer_origin, designer_user) or waiting_for_user wi Inputs: unlink |
list_dataverse_views | Microsoft Copilot only (Entra sign-in): lists the Dynamics 365 account views the signed-in user can read, so their accounts import without a file. Without environment_url it lists the user's environments; with one environment it goes straig Inputs: environment_url |
list_designer_projects | Lists the EasyTerritory Designer rolodex projects the linked Designer user can read: project_id, label, description, tags, saved_at, is_mine, and layers (point data present). q filters by text, tag by rolodex tag, mine=true to the user's ow Inputs: q, tag, mine |
list_part_layers | Returns 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: part_layer, label, d Inputs: part_layer, country_code |
load_analysis_panel | Shows a completed analyze result in the open map's analysis dock (single or compare). Needs map_session_id and the analyze task_id/job_id or the full analyze result (with tal_analyses and ts_identity; a partial object returns INVALID_REQUES Inputs: map_session_id, analyses, labels, roles, presentation_mode, task_id |
points_in_territory | Lists 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 of sample_size points Inputs: tal_id, territory_id, territory_ids, point_layer, point_filter, metrics |
publish_to_dataverse | Microsoft Copilot (Entra sign-in): writes stamped point-layer columns back to Dynamics 365 accounts keyed by accountid (1:1 Account PATCH). Needs map_session_id or ts_handle. territory_id / territory_label are computed at publish for one al Inputs: environment_url, point_layer, field_map, include_unassigned, confirm, map_session_id |
push_to_designer | Saves a Territory Solution in EasyTerritory Designer from the server. Without project_id it creates a new rolodex project named label (the user's choice; a missing label returns CLARIFICATION_REQUIRED). With project_id it overwrites that pr Inputs: ts_handle, job_id, map_session_id, project_id, label, part_layer_id |
query_parts, realign, reintegrate_branch, request_account_upload, request_assignment_upload, request_part_selection, schedule_visits, seed_build, set_map_state, show_map_overlay, submit_feedback, tasks_cancel, tasks_get, tasks_result, territory_merge, territory_rebalance, territory_split, workflow_advisor
Every block below points at https://mcp.easyterritory.ai/. Pick your client and copy.
claude mcp add --transport http easyterritory https://mcp.easyterritory.ai/
{
"mcpServers": {
"easyterritory": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.easyterritory.ai/"]
}
}
}{
"mcpServers": {
"easyterritory": {
"url": "https://mcp.easyterritory.ai/"
}
}
}{
"servers": {
"easyterritory": {
"type": "http",
"url": "https://mcp.easyterritory.ai/"
}
}
}{
"context_servers": {
"easyterritory": {
"url": "https://mcp.easyterritory.ai/"
}
}
}{
"mcpServers": {
"easyterritory": {
"serverUrl": "https://mcp.easyterritory.ai/"
}
}
}{
"mcpServers": {
"easyterritory": {
"url": "https://mcp.easyterritory.ai/"
}
}
}name: EasyTerritory
version: 0.0.1
schema: v1
mcpServers:
- name: EasyTerritory
type: streamable-http
url: https://mcp.easyterritory.ai/{
"mcpServers": {
"easyterritory": {
"httpUrl": "https://mcp.easyterritory.ai/"
}
}
}{
"mcpServers": {
"easyterritory": {
"type": "http",
"url": "https://mcp.easyterritory.ai/"
}
}
}{
"mcpServers": {
"easyterritory": {
"url": "https://mcp.easyterritory.ai/"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.easyterritory.ai%2F&type=streamable_http&id=easyterritory&name=EasyTerritory
It answered our last check on 15 November 2026 in 333 ms. Over 4 checks since 29 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by easyterritory.ai and served from mcp.easyterritory.ai, the vendor's own domain: https://mcp.easyterritory.ai/.
58, as returned by the server's own tools/list on 18 November 2026: account_build, analyze, analyze_network_coverage, analyze_routes, auto_build, calculate_route, cluster_points, configure_map, and 50 more.
It answered our last check on 15 November 2026 in 333 ms. Over 4 checks since 29 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.easyterritory.ai/. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: ai.easyterritory. Endpoint host: mcp.easyterritory.ai. ARD identifier: urn:air:ai.easyterritory:mcp:ezt-mcp.
First indexed 29 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.