mHelpDesk MCP server Let your AI agent run the mHelpDesk office.

ToolWhat it doesAccess

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

  Returns customers with ID, service locations, open jobs and balance.

  MCP callmhelpdesk_read → list_customers

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

  Parameters

  Parameters: list_customers

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

  Example response

  {
    "customers": [
      {
        "customer_id": "MC-30221",
        "name": "Jim and Carol Hendricks",
        "location": "715 E 62nd St, Indianapolis, IN",
        "open_jobs": 1,
        "balance": "0.00"
      }
    ],
    "page": 1
  }

• create_lead Creates a lead from a call or form. write

  Adds the lead with contact, location and request. Reaches no one, so it runs at once.

  MCP callmhelpdesk_write → create_lead

  REST endpointPOST https://cotlet.dev/api/v1/mhelpdesk/leads

  Parameters

  Parameters: create_lead

  Name	Type	Description
  name string required	string	Customer name.
  address string required	string	Service location.
  phone string	string	Phone.
  request string required	string	What they need.

  Example input

  {
    "name": "Jane Doe",
    "address": "address",
    "request": "request"
  }

  Example response

  {
    "lead_id": "L-55102",
    "name": "Angela Ruiz",
    "request": "AC not cooling, upstairs",
    "status": "New"
  }

• create_estimate Drafts an estimate from your price list. write

  Creates the estimate for the customer or lead from price list items. Sending it is a separate step in mHelpDesk, so drafting runs at once.

  MCP callmhelpdesk_write → create_estimate

  REST endpointPOST https://cotlet.dev/api/v1/mhelpdesk/customers/{customer_id}/estimates

  Parameters

  Parameters: create_estimate

  Name	Type	Description
  customer_id string required	string	Customer ID from list_customers.
  items array required	array	Price list item, quantity, price.

  Example input

  {
    "customer_id": "customer_8c41d2",
    "items": "items"
  }

  Example response

  {
    "estimate_id": "E-20418",
    "customer": "Angela Ruiz",
    "total": "1,240.00",
    "status": "Draft"
  }

ToolWhat it doesAccess

• list_jobs Jobs by status or date, with tech and schedule. read

  Returns jobs with customer, status, assigned tech and scheduled time.

  MCP callmhelpdesk_read → list_jobs

  REST endpointGET https://cotlet.dev/api/v1/mhelpdesk/jobs

  Parameters

  Parameters: list_jobs

  Name	Type	Description
  status string	string	Job status as in your settings.
  date_from string	string	ISO date.
  date_to string	string	ISO date.
  page integer	integer	Page number. Default: 1.

  Example response

  {
    "jobs": [
      {
        "job_id": "J-81120",
        "customer": "Brookside Apartments LLC",
        "status": "Scheduled",
        "tech": "Ray",
        "start": "2026-11-10T08:00"
      }
    ],
    "page": 1
  }

• schedule_job Creates a job and puts it on the schedule with a tech. writeasks first

  Creates the job, from an estimate if you give one, and schedules the appointment. Your settings decide whether the customer gets a notice. By default you confirm each call; you can switch that off for this tool.

  MCP callmhelpdesk_write → schedule_job

  REST endpointPOST https://cotlet.dev/api/v1/mhelpdesk/customers/{customer_id}/job/schedule

  Parameters

  Parameters: schedule_job

  Name	Type	Description
  customer_id string required	string	Customer ID from list_customers.
  start string required	string	ISO date and time.
  tech string	string	Technician.
  estimate_id string	string	Estimate to copy to the job.
  description string	string	Work to do.

  Example input

  {
    "customer_id": "MC-30288",
    "start": "2026-11-11T13:00",
    "tech": "Ray",
    "estimate_id": "E-20418"
  }

  Example response

  {
    "job_id": "J-81177",
    "customer": "Angela Ruiz",
    "tech": "Ray",
    "start": "2026-11-11T13:00",
    "status": "Scheduled"
  }

ToolWhat it doesAccess

• create_invoice Drafts an invoice for a completed job. write

  Creates the invoice from the job's items. Sending or charging it stays a step you take, so drafting runs at once.

  MCP callmhelpdesk_write → create_invoice

  REST endpointPOST https://cotlet.dev/api/v1/mhelpdesk/jobs/{job_id}/invoices

  Parameters

  Parameters: create_invoice

  Name	Type	Description
  job_id string required	string	Job ID from list_jobs.

  Example input

  {
    "job_id": "job_8c41d2"
  }

  Example response

  {
    "invoice_id": "INV-44021",
    "job": "J-81120",
    "total": "385.00",
    "status": "Draft"
  }

• list_unpaid_invoices Invoices with a balance, oldest first. read

  Returns invoices with customer, balance and days since issued.

  MCP callmhelpdesk_read → list_unpaid_invoices

  REST endpointGET https://cotlet.dev/api/v1/mhelpdesk/unpaid-invoices

  Parameters

  Parameters: list_unpaid_invoices

  Name	Type	Description
  min_days integer	integer	Only invoices issued at least this many days ago.

  Example response

  {
    "invoices": [
      {
        "invoice_id": "INV-43910",
        "customer": "Brookside Apartments LLC",
        "balance": "1,120.00",
        "days": 34
      }
    ]
  }