Simpro MCP server: connect Simpro to Claude and ChatGPT

Simpro is reached through its API with read-only credentials your administrator authorises. Junction builds only read requests, applies the API's paging and rate limits, and adds its own limits and sensitivity rules on top. Simpro's API reference is public.

• “Which jobs are over their quoted cost?”
• “Which invoices are unpaid after 30 days?”
• “Which quotes are still waiting for a customer decision?”

Answers come from your own system, with the source rows and the time the data was last updated.

• Not available yet. Simpro is in Junction's next wave of systems: widely used (markets: Australia, United Kingdom, United States) and readable without writing to it. We build each mapping from the vendor's own reference and check it with a customer who runs the system before calling it live.
• Integration routes found in our research: REST API, Webhooks.
• When we researched this in October 2026 the vendor offered no MCP server of its own; only unofficial, community-built ones existed.
• Payroll and personal data are denied by default.

Is there an MCP server for Simpro?

Not yet. Junction is a read-only MCP server for construction software, and Simpro is in its next wave of systems. It is not available today; tell us you run Simpro and it moves up the list.

Is Simpro supported today?

No. Simpro is in our next wave, which means it is next in line to be built, not that it works today. Tell us you run it and it moves up the list.

Can the AI change anything in Simpro?

No. Junction is read-only: it cannot create, edit or delete a record.