RazorSync MCP server Let your AI agent run the RazorSync office work.

ToolWhat it doesAccess

• list_customers Customers, searchable by name, phone, email or address. read

  Returns customers with ID, contact details and service locations. Pass the customer_id to create_work_order.

  MCP callrazorsync_read → list_customers

  REST endpointGET https://cotlet.dev/api/v1/razorsync/customers

  Parameters

  Parameters: list_customers

  Name	Type	Description
  query string	string	Name, phone, email or street address.
  page integer	integer	Page number. Default: 1.

  Example response

  {
    "customers": [
      {
        "customer_id": "30418",
        "name": "Greenway Apartments",
        "phone": "555-0193",
        "email": "office@example.com",
        "service_address": "220 Elm Ave, Columbus, OH 43215"
      }
    ],
    "page": 1
  }

• create_customer Adds a customer with a service location. write

  Creates the customer and its first service location. Search list_customers first so a repeat caller does not become a duplicate. Reaches no one, so it runs at once.

  MCP callrazorsync_write → create_customer

  REST endpointPOST https://cotlet.dev/api/v1/razorsync/customers

  Parameters

  Parameters: create_customer

  Name	Type	Description
  name string required	string	Customer or company name.
  phone string	string	Phone number.
  email string	string	Email.
  service_address string required	string	Street, city, state and ZIP.

  Example input

  {
    "name": "Jane Doe",
    "service_address": "service address"
  }

  Example response

  {
    "customer_id": "30502",
    "name": "Priya Nair",
    "service_address": "18 Cedar Ct, Columbus, OH 43206"
  }

ToolWhat it doesAccess

• list_work_orders Work orders by date, status or technician. read

  Returns work orders with customer, description, technician, scheduled time and status.

  MCP callrazorsync_read → list_work_orders

  REST endpointGET https://cotlet.dev/api/v1/razorsync/work-orders

  Parameters

  Parameters: list_work_orders

  Name	Type	Description
  date_from string	string	ISO date.
  date_to string	string	ISO date.
  status string	string	unscheduled, scheduled, in_progress or complete.
  technician string	string	Technician name.
  page integer	integer	Page number. Default: 1.

  Example response

  {
    "work_orders": [
      {
        "work_order_id": "WO-7731",
        "customer": "Greenway Apartments",
        "description": "Unit 4B dishwasher leak",
        "technician": "Marcus",
        "scheduled": "2026-11-12T09:00",
        "status": "Scheduled"
      }
    ],
    "page": 1
  }

• create_work_order Opens a work order for a customer. write

  Creates the work order with description and service location. It stays unscheduled until schedule_work_order, so it runs at once.

  MCP callrazorsync_write → create_work_order

  REST endpointPOST https://cotlet.dev/api/v1/razorsync/customers/{customer_id}/work-orders

  Parameters

  Parameters: create_work_order

  Name	Type	Description
  customer_id string required	string	Customer ID from list_customers.
  description string required	string	What the customer needs.
  service_type string	string	Service type as named in your account.

  Example input

  {
    "customer_id": "customer_8c41d2",
    "description": "description"
  }

  Example response

  {
    "work_order_id": "WO-7790",
    "customer": "Priya Nair",
    "description": "Garbage disposal not working",
    "status": "Unscheduled"
  }

• schedule_work_order Assigns a work order to a technician and a time. writeasks first

  Puts the work order on the technician's schedule. Your RazorSync notification settings decide whether the customer gets a message. By default you confirm each call; you can switch that off for this tool.

  MCP callrazorsync_write → schedule_work_order

  REST endpointPOST https://cotlet.dev/api/v1/razorsync/work-orders/{work_order_id}/schedule

  Parameters

  Parameters: schedule_work_order

  Name	Type	Description
  work_order_id string required	string	Work order number from list_work_orders.
  technician string required	string	Technician name.
  start string required	string	ISO date and time.
  duration_min integer	integer	Minutes. Default: 60.

  Example input

  {
    "work_order_id": "WO-7790",
    "technician": "Marcus",
    "start": "2026-11-13T14:00",
    "duration_min": 90
  }

  Example response

  {
    "work_order_id": "WO-7790",
    "technician": "Marcus",
    "scheduled": "2026-11-13T14:00",
    "status": "Scheduled"
  }

ToolWhat it doesAccess

• list_invoices Invoices by status, customer or age, with balances. read

  Returns invoices with total, balance and status. Use status unpaid and older_than_days for a collections list.

  MCP callrazorsync_read → list_invoices

  REST endpointGET https://cotlet.dev/api/v1/razorsync/invoices

  Parameters

  Parameters: list_invoices

  Name	Type	Description
  status string	string	unpaid, paid or all. Default: all.
  older_than_days integer	integer	Only invoices older than this.
  page integer	integer	Page number. Default: 1.

  Example response

  {
    "invoices": [
      {
        "invoice_id": "INV-4410",
        "customer": "Greenway Apartments",
        "total": "1,180.00",
        "balance": "1,180.00",
        "date": "2026-10-05",
        "status": "Unpaid"
      }
    ],
    "page": 1
  }

• create_invoice Builds the invoice for a completed work order. write

  Creates the invoice from the work order's line items. It stays unsent until send_invoice, so it runs at once.

  MCP callrazorsync_write → create_invoice

  REST endpointPOST https://cotlet.dev/api/v1/razorsync/work-orders/{work_order_id}/invoices

  Parameters

  Parameters: create_invoice

  Name	Type	Description
  work_order_id string required	string	Work order number from list_work_orders.

  Example input

  {
    "work_order_id": "work_order_8c41d2"
  }

  Example response

  {
    "invoice_id": "INV-4472",
    "work_order_id": "WO-7731",
    "total": "265.00",
    "status": "Unsent"
  }

• send_invoice Emails an invoice to the customer. writeasks first

  Sends the invoice to the customer's billing email or the addresses you pass. By default you confirm each call; you can switch that off for this tool.

  MCP callrazorsync_write → send_invoice

  REST endpointPOST https://cotlet.dev/api/v1/razorsync/invoices/{invoice_id}

  Parameters

  Parameters: send_invoice

  Name	Type	Description
  invoice_id string required	string	Invoice number from list_invoices.
  to string[]	string[]	Recipient emails. Default: the customer's billing email.

  Example input

  {
    "invoice_id": "invoice_8c41d2"
  }

  Example response

  {
    "invoice_id": "INV-4472",
    "status": "Sent",
    "sent_to": [
      "office@example.com"
    ],
    "total": "265.00"
  }

• record_payment Logs a check, cash or other manual payment on an invoice. writeasks first

  Adds the payment and lowers the balance. No card is charged. By default you confirm each call; you can switch that off for this tool.

  MCP callrazorsync_write → record_payment

  REST endpointPOST https://cotlet.dev/api/v1/razorsync/invoices/{invoice_id}/payments

  Parameters

  Parameters: record_payment

  Name	Type	Description
  invoice_id string required	string	Invoice number from list_invoices.
  amount string required	string	Amount, e.g. 1180.00.
  method string required	string	check, cash or other.
  reference string	string	Check number or note.

  Example input

  {
    "invoice_id": "invoice_8c41d2",
    "amount": "amount",
    "method": "method"
  }

  Example response

  {
    "invoice_id": "INV-4410",
    "payment": {
      "method": "Check",
      "amount": "1,180.00",
      "reference": "2209"
    },
    "balance": "0.00"
  }