Documented master-data API
The current public REST API covers assets, categories, custom fields, locations, people and account users. It does not currently expose public work-order, form-submission, inventory, maintenance or meter resources.
Roadmap, not generally available
MapTrack MCP roadmap and integration planning
MapTrack does not currently ship a hosted MCP server. We can help enterprise teams assess a customer-specific AI integration using today's public master-data API, manual file exchange and automation webhooks, while separately scoping the execution APIs and controls a production MCP service would require.
Not liveno hosted MCP endpoint today
6 groupscurrent public API coverage
Customsecurity and delivery scope required
Availability boundary
There is no public MapTrack MCP endpoint, paid-plan entitlement or production read/write MCP service today. An integration workshop is a discovery and engineering engagement, not activation of a prebuilt connector. Capability boundary reviewed 12 July 2026.
Available today
Start with the interfaces that actually ship
The first architecture decision is whether the required workflow fits MapTrack's current integration surface. These are building blocks for a scoped project, not an ERP or MCP connector.
Manual file exchange
CSV/XLSX import currently covers assets, locations and people. On-demand exports are available for selected operational records, but scheduled enterprise exchange is not a shipped capability.
Automation webhooks
Rules can send outbound HTTP POST actions for configured events. Enterprise retry, idempotency, replay and dead-letter behaviour must be designed separately for any production integration.
Production readiness
What must exist before MCP can be called enterprise-ready
A protocol endpoint is the easy part. A production service needs controls around identity, tenancy, write safety, observability and recovery. Those controls must be proven before MapTrack markets a hosted MCP capability as available.
Review the integration architecture guide- A least-privilege identity and permission model for every AI client
- A versioned tool contract limited to verified MapTrack API resources
- Human confirmation for consequential create or update actions
- Idempotency, retry, replay and exception handling for every write path
- Immutable audit evidence linking the user, client, request and result
- Tenant isolation, rate limits, revocation and production monitoring
Scope the workflow before committing to the protocol
Map the user questions, approved actions, source-of-truth rules and exception paths first. MapTrack can then help determine what is possible now, what needs custom engineering and what remains roadmap.
MCP roadmap FAQs
Current answers about MapTrack, MCP and customer-specific AI integration work.
- Does MapTrack currently offer a hosted MCP server?
- No. MapTrack does not currently ship a public or generally available hosted MCP server. This page documents the roadmap and the controls required to scope a customer-specific AI or MCP integration without presenting it as a live product capability.
- Can I connect Claude, ChatGPT or Cursor to MapTrack today?
- There is no MapTrack-hosted MCP endpoint to connect those clients to today. A customer can discuss a custom integration architecture with MapTrack and its IT or integration partner, limited to the data and operations available through approved interfaces.
- What integration tools are available now?
- MapTrack currently provides a documented public REST API for six master-data resource groups, manual CSV/XLSX import and export, and outbound automation webhooks. Coverage and operational controls must be verified against the project requirements before a production commitment is made.
- Can a custom MCP gateway manage ERP work orders?
- Not through MapTrack's current public API alone. Public work-order, form-submission, inventory, maintenance and meter resources are not currently shipped. Any ERP work-order or evidence exchange needs separately engineered middleware, approved ERP interfaces and a tested ownership contract.
- When will the MapTrack MCP server be available?
- MapTrack has not published a general-availability date. Availability should only be communicated after the service is merged, deployed, security reviewed, documented and verified in production. Open or draft development work is not a customer commitment.
Bring the use case. Leave with an honest boundary
We'll separate current MapTrack capability, customer-specific build work and future roadmap before anyone commits to a delivery plan.