EasyTerritory MCP
ai.easyterritory/ezt-mcp
Build, balance, realign and analyze sales/service territories; geocode, route, schedule, live map.
Indexed
Crawled from a public source. No check has passed yet, or a check failed.
Tiers are set by checks and outcomes only. Nobody can pay for a tier or a higher rank. How we check
What it can reach
From its install config and its own description; a sandbox run will confirm this later.
- mcp.easyterritory.ai
- local files (paths not stated)
- None seen
Checks on v0.1.0
Real tool
passrules 2026-09-29.1 · 3 hours agoStatic scan
failrules 2026-09-29.1 · 3 hours ago- criticalPairs a secret with an instruction to send data.tool:geocode_address.description
- criticalPairs a secret with an instruction to send data.tool:export_geojson.description
Install
Each app still asks you to confirm. Everything is pinned to the version checked above.
code --add-mcp '{"name":"ezt-mcp","type":"http","url":"https://mcp.easyterritory.ai/"}'{
"servers": {
"ezt-mcp": {
"type": "http",
"url": "https://mcp.easyterritory.ai/"
}
}
}- 1.Click the link, or run the command.
- 2.VS Code asks you to confirm the server before it starts.
Pinned to v0.1.0 · 853ed98de751
Tools it offers
As the server describes them. This text comes from the publisher and is shown as-is.
get_map_visualization[Tier 1 — MC-First Entry] FIRST step of non-headless territory work (invariant I-1). When: open a blank map for planning, or open/reuse the user's Map Component for an existing Territory Solution (TS), ts_handle, or completed job. Pass new_project=true to replace the live workspace with an empty project; omitted empty+view reuses the existing project. Optional presentation.view_name: empty | points_only | review | selection (defaults from mode/TS content). Diagnostics: presentation.debug_panel=true. Prerequisites: none (idempotent per user_id). Next: hand user map_url, then ensure_map_viewer until viewer_status.connected. Dual surface (same map_session_id, one map): Apps-capable hosts render this map in chat from ui://easyterritory/map-viewer (_meta.ui.resourceUri); every other client — including Cursor — opens map_url in a browser tab. map_url is always returned. Do not open a second surface or call this tool again to 'fix' a map. Scenarios: MC-000, MC-001, MV-001, S004.
get_guidance[Tier 1 — Startup Guide + Handle] CALL THIS FIRST. Read-only. When: session start, after blocked_by=guidance_required, or when the shared rules are unclear. Returns result.text (the short cross-tool brief, same text as server instructions) and result.guidance_handle (the rotating code every territory/map tool requires). Per-tool rules are on that tool's description. Workflow essays are inlined as guidance on discover_intent, workflow_advisor, and blocked_by. Exempt: get_guidance, submit_feedback, discover_intent, workflow_advisor, ep_* tools.
discover_intent[Tier 1 — Router] Deterministic entry point for ambiguous or open-ended territory requests. When: the user's goal or build type is unclear and you want the correct workflow before acting. Prerequisites: none (static keyword routing; no compute). Returns an intent_category, the recommended tool order, the Tier 1 tool + Tier 2 alternatives, required_inputs, clarifying_questions to ask when inputs are missing, a guidance_uri (ezt://guidance/workflows/{name}) for the full atom, and `guidance` — the same EMEP atom inlined as {uri, title, excerpt, truncated}, so you do NOT need a second resources/read to get the workflow text. Use it to disambiguate auto_build vs account_build vs direct_build and to route realign / restructure / analyze / delegation / geocode-ingest / load-part-layer-on-map (add zips, show zip codes) / route-stops (drive a list of stops in the best order) / reachable-area (a drive-time or drive-distance area around origins — service area, catchment, coverage, isochrone, which routes to isochrone_build) / periodic-scheduling (a recurring cadence — 'every 30 days', 'twice a month' — and which day each visit lands on, which routes to schedule_visits, never auto_build or cluster_points) / push-to-designer (an EasyTerritory Designer rolodex project from a TS: export_geojson then POST FromTerritorySolution to create or PUT .../Projects/{projectId}/... to update; territories, points, and routes import; ezt_pat_; there is no MCP push tool) / pull-from-designer (a Designer rolodex project into the MCP: GET REST/Agent/Projects then GET .../Projects/{projectId}/TerritorySolution with ezt_pat_, then import_geojson geojson_gzip; there is no MCP pull tool). Scenarios: AB-016, ACB-003, wrong-build-tool.
Versions
- v0.1.0 · Sep 29, 2026
Signals
- Installs through us
- 0
- Agent reports
- none yet
- Publisher
- ai.easyterritory · unclaimed
- Found via
- registry