Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Simpro to Claude Code

Make Claude draft quotes and create jobs in Simpro. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Simpro to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Simpro, you add a Simpro MCP server: a small hosted service that exposes Simpro's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Simpro account. No API keys pasted into config files.

claude mcp add --transport http simpro https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Simpro once connected?

Full read-write lets Claude work the quote-to-cash flow. It can draft a quote for a customer site, convert it to a job once you approve, check schedules and cost centers, update customer records, and answer questions like which jobs are running over budget or which invoices are still unpaid.

  • Draft a quote for a customer and site, saved for your review
  • Convert an approved quote into a job after you approve
  • Pull job status, sections, and cost centers for any active job
  • Create or update customer and site records after you approve
  • Check technician schedules and upcoming bookings for the week
  • Report on open invoices and payment status across jobs

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Simpro access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Simpro API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Simpro changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Simpro connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Simpro connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Simpro account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Simpro's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Simpro?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Simpro account it signs in with. Revoking access is one click in Simpro.

More on the Simpro connector

Simpro connector for claude.aiServiceTitan + Claude CodeFieldEdge + Claude CodeJobber + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us