← All integrations

RepairShopr MCP server

18 operations0 webhooks

Repair desk and ticketing with RepairShopr - read and write customers, tickets, invoices and products, and list contact people and vendors, against a RepairShopr account's own subdomain.

Use RepairShopr in Claude, ChatGPT, Cursor or another MCP client

Connect RepairShopr once in Corsair, then add one MCP address to your agent.

Connect RepairShopr
Setup steps for Claude, ChatGPT, Cursor and Claude Code

Building your own app on the Corsair SDK? Get API keys

Try RepairShopr with your agent

Connect RepairShopr, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in RepairShopr on my account, then run one read-only example and show me the result.

Runs once, when you ask

RepairShopr tools and triggers

Tools are what your agent can do in RepairShopr through Corsair's MCP server. Triggers are the RepairShopr events a routine can start from.

Customers

  • CreateWrite

    Create a customer from a business name or a person name, with contact details and notification settings

    customers.create

  • DeleteDestructive

    Delete a customer permanently

    customers.delete

  • GetRead-only

    Fetch one customer with their contact details, addresses and custom fields

    customers.get

  • ListRead-only

    List customers with name, email and id filters, an optional sort, and page paging

    customers.list

  • UpdateWrite

    Update a customer: their name, addresses, contact details or notification settings

    customers.update

Tickets

  • CreateWrite

    Create a ticket for a customer with its subject, status, priority, assignee and assets

    tickets.create

  • DeleteDestructive

    Delete a ticket permanently

    tickets.delete

  • GetRead-only

    Fetch one ticket with its customer, location, status, priority and custom fields

    tickets.get

  • ListRead-only

    List tickets with customer, contact, status, assignee and date filters, plus page paging

    tickets.list

  • UpdateWrite

    Update a ticket: its subject, status, priority, assignee or due date

    tickets.update

Products

  • CreateWrite

    Create a product; the name and description are both required by RepairShopr

    products.create

  • GetRead-only

    Fetch one product with its pricing, stock level, warranty and category

    products.get

Connect RepairShopr to Claude, ChatGPT or Cursor

  1. 1

    Connect RepairShopr in Corsair

    Add your RepairShopr API key once in Corsair. Corsair stores the credential encrypted and makes the RepairShopr API calls for your agent, so it never goes into a prompt or a config file. Connect RepairShopr

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs RepairShopr. On a ChatGPT personal plan, connect RepairShopr here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, RepairShopr's read and write operations run right away and its 2 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/repairshopr, add the RepairShopr plugin, and connect with an API key. Then call methods like corsair.repairshopr.api.contacts.list() from your app. Corsair keeps each tenant isolated.

Yes. RepairShopr requires an API key from your RepairShopr account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit RepairShopr, GitHub, Notion, Stripe, and the rest. Trigger RepairShopr from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for repair desk and ticketing with RepairShopr - read and write customers, tickets, invoices and products, and list contact people and vendors, against a RepairShopr account's own subdomain. Common builds include sync jobs, admin tooling, and agents that call RepairShopr APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per RepairShopr API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/repairshopr in the open repo. When RepairShopr ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your RepairShopr data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store RepairShopr data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put RepairShopr on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 2 destructive RepairShopr operations. You can change a link's mode at hub.corsair.dev/me.