Connect Shopmonkey to Claude Code

Make Claude write work orders and book appointments in Shopmonkey. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Shopmonkey to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Shopmonkey, you add a Shopmonkey MCP server: a small hosted service that exposes Shopmonkey'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 Shopmonkey account. No API keys pasted into config files.

claude mcp add --transport http shopmonkey 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 Shopmonkey once connected?

Full read-write lets Claude run the front counter. It can write up a work order for a customer and vehicle, book or move appointments once you approve, update customer records, check parts and labor items, and answer questions like which orders are stuck in a workflow stage or still unpaid.

Create a work order for a customer and vehicle, held for your review
Book or reschedule an appointment after you approve
Add or update customer and vehicle records after you approve
Pull open orders by workflow stage across the shop
Check parts, tires, and labor items in inventory
Report on invoices and payments for any date range

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 Shopmonkey 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 Shopmonkey API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Shopmonkey 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 Shopmonkey 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 Shopmonkey 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 Shopmonkey 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 Shopmonkey'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 Shopmonkey?

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 Shopmonkey account it signs in with. Revoking access is one click in Shopmonkey.

More on the Shopmonkey connector

Shopmonkey connector for claude.ai ServiceTitan + Claude Code Workiz + Claude Code QuickBooks Online + 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 connector Talk to us