Early access
MCP Server
MCP Server (early access) brings EasyTerritory capability to your AI agent. Built on the same tools as Territory Designer, it lets Claude, Copilot, Grok Bot, or any MCP-compatible host build, balance, realign, and analyze territories. MCP can route, schedule, analyze coverage, and share the results. Run a one-off scenario on the live MCP Map or a repeatable headless workflow: your agent handles the heavy lifting, and you make the strategic calls.
Territory intelligence, on autopilot
Start from the data you already have: a spreadsheet of accounts, a CRM export, or an existing alignment file. The MCP Server geocodes it, builds, rebalances, schedules, routes, analyzes and shares. It has 58 tools and works through plain conversation.
What it can do
MCP Server is built for sales operations leaders and territory planners, and for the teams who run field service, franchise development, and contractor networks. Because it is built on the same tools as Territory Designer, you and your agent choose the approach: hands-on with the integrated map, or fully automated. Every tool works with or without a visual interface. Your agent pulls data from your cloud data platform (Microsoft Fabric, Snowflake, Redshift, BigQuery, Databricks), your CRM, or a simple file, then uses MCP for territory realignment, routing, or scheduling, with consistent, repeatable results.
Intelligent Territory Management
Build balanced territories from scratch or from existing alignment files. Set your goals (territory count, workload targets, balance metrics) and let your agent do the rest. Convert account-based alignments to territory regions and grow franchise zones from a seed location and target metric. As data changes, realign postal codes, split, merge, or rebalance territories, keeping changes as local as possible. Analyze balance and workload distribution, compare alignment scenarios side by side, and share read-only views with stakeholders.
Optimized Routing & Scheduling
Calculate optimized multi-stop routes with stop-priority banding in loop, one-way, or open formats, with per-route drive and onsite hours. Build recurring visit schedules that cluster accounts into daily work buckets by cadence and an hour cap you set, with calendar start dates, blackout dates, and due dates, so every visit lands inside its service window and SLA commitments are met. Find contractor coverage gaps by trade with Service Network Coverage before they turn into missed response times.
Roundtrip with Territory Designer
MCP Server works roundtrip with Territory Designer. Pull a Designer project into your agent with its territories, point layers, and styles intact, run automated territory management workflows, then push the result back to the same project for review. Work can start on either side: territories your agent builds from scratch in MCP can be pushed into Designer as a brand-new project, ready for planners to refine. Planners stay in control: agents do the heavy lifting, and every change can be approved in Designer before it becomes the system of record.
Why EasyTerritory MCP
- Hosted by EasyTerritory — not self-hosted. Customers connect their agent and go.
- Your organization owns its data — EZT MCP is never your system of record. Working data is deleted automatically about 1 hour after last use, logs keep metadata only (not your rows), and your data is never used to train AI models. See our Privacy Policy.
- It asks before it guesses — if a dwell time, drive-time limit, or start date is missing, the server asks instead of inventing a default.
- Standard GeoJSON in and out — no proprietary formats. Push your alignments to Territory Designer for hands-on refinement when you need it.
- ExpertPack knowledge layer — encodes a decade of territory design expertise that is not found in foundation AI models.
- MCP specification compatible — the server negotiates protocol version 2025-11-25, and accepts 2025-06-18 and 2025-03-26.
- Wide international postal-code support — build territories from postal areas in many countries. See the full list of supported countries.
- Full documentation — setup guides, tool reference, and examples to get you started.
- Secure Microsoft Dataverse and Entra ID access — in Microsoft Copilot, people sign in with their Entra ID account and the server reads their Dynamics 365 account views as them, so it sees only what their Dynamics role allows. Up to 100,000 accounts per view load straight into EasyTerritory without an export, so big data stays out of your AI agent’s context.
