ConnectWise MCP server Let your AI agent work your ConnectWise tickets.

ToolWhat it doesAccess

• list_service_boards List the service boards with their statuses, types, subtypes and items. read

  Returns each board with the values you can set on a ticket: statuses, types, subtypes and items. These are the values of the board setup in PSA, so a ticket can only use the ones that exist on its board. Run it once before update_ticket or create_ticket, so the agent uses real names. What you see follows your security role.

  MCP callconnectwise_read → list_service_boards

  REST endpointGET https://cotlet.dev/api/v1/connectwise/service-boards

  Parameters

  Parameters: list_service_boards

  Name	Type	Description
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "boards": [
      {
        "id": 1,
        "name": "Service Desk",
        "statuses": [
          "New",
          "In Progress",
          "Waiting on Client",
          "Closed"
        ],
        "types": [
          "Incident",
          "Request"
        ],
        "subtypes": [
          "Email",
          "Printing"
        ],
        "items": [
          "Outlook",
          "Printer"
        ]
      },
      {
        "id": 2,
        "name": "Projects",
        "statuses": [
          "Scheduled",
          "In Progress",
          "Closed"
        ],
        "types": [
          "Project task"
        ],
        "subtypes": [],
        "items": []
      }
    ],
    "next_cursor": null
  }

• list_tickets List service tickets, filtered by board, status, priority, owner, company or text. read

  Returns one row per ticket with number, summary, company, board, status, priority, owner and the date of the last update. The most recently updated tickets come first. Without a filter it lists the tickets your role can see, one page at a time. Follow next_cursor until it comes back empty.

  MCP callconnectwise_read → list_tickets

  REST endpointGET https://cotlet.dev/api/v1/connectwise/tickets

  Parameters

  Parameters: list_tickets

  Name	Type	Description
  board string	string	Board name from list_service_boards.
  status string	string	Status name on that board, for example "New".
  priority string	string	Priority name as shown on the ticket.
  owner string	string	Member identifier of the ticket owner.
  company string	string	Company identifier from search_companies.
  query string	string	Text to find in the ticket summary.
  updated_before string	string	ISO date. Only tickets last updated before this day.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "tickets": [
      {
        "ticket_id": 30412,
        "summary": "Printer queue stuck on floor 2",
        "company": "Northwind Dental",
        "board": "Service Desk",
        "status": "New",
        "priority": "Priority 2 - High",
        "owner": null,
        "updated_at": "2026-11-05T08:41:00Z"
      },
      {
        "ticket_id": 30398,
        "summary": "New starter needs laptop and mailbox",
        "company": "Acme Logistics",
        "board": "Service Desk",
        "status": "In Progress",
        "priority": "Priority 3 - Normal",
        "owner": "mreyes",
        "updated_at": "2026-11-04T15:12:00Z"
      }
    ],
    "next_cursor": null
  }

• get_ticket Read one service ticket with its fields, resources and latest notes. read

  Returns the ticket header: summary, company, contact, board, status, type, subtype, item, priority and owner. It also returns the last 5 notes from the Discussion, Internal and Resolution tabs, so the agent can read before it acts. For the full thread use list_ticket_notes.

  MCP callconnectwise_read → get_ticket

  REST endpointGET https://cotlet.dev/api/v1/connectwise/tickets/{ticket_id}

  Parameters

  Parameters: get_ticket

  Name	Type	Description
  ticket_id integer required	integer	Ticket number from list_tickets or get_ticket.

  Example input

  {
    "ticket_id": 1
  }

  Example response

  {
    "ticket_id": 30412,
    "summary": "Printer queue stuck on floor 2",
    "company": "Northwind Dental",
    "contact": "Dana Whitfield",
    "board": "Service Desk",
    "status": "New",
    "type": "Incident",
    "subtype": "Printing",
    "item": "Printer",
    "priority": "Priority 2 - High",
    "owner": null,
    "latest_notes": [
      {
        "note_id": 884102,
        "note_type": "discussion",
        "author": "Dana Whitfield",
        "created_at": "2026-11-05T08:41:00Z",
        "text": "Nothing prints since 8 am. Three people are waiting."
      }
    ]
  }

• create_ticket Create a service ticket on a board. writeasks first

  Creates the ticket and returns its number. It lands on the board like a ticket created by hand, so anything your board does for new tickets runs. A board that does not exist, or a status or type that is not on that board, fails without creating anything. By default you confirm each call; you can switch that off for this tool.

  MCP callconnectwise_write → create_ticket

  REST endpointPOST https://cotlet.dev/api/v1/connectwise/tickets

  Parameters

  Parameters: create_ticket

  Name	Type	Description
  summary string required	string	Ticket summary, one line.
  company string required	string	Company identifier from search_companies.
  board string required	string	Board name from list_service_boards.
  status string	string	Status on that board. The board default when left out.
  priority string	string	Priority name as shown on the ticket.
  type string	string	Type from list_service_boards.
  owner string	string	Member identifier of the owner.
  description string	string	First note of the ticket, added as a Discussion note.

  Example input

  {
    "summary": "summary",
    "company": "company",
    "board": "board"
  }

  Example response

  {
    "ticket_id": 30431,
    "summary": "Quarterly review",
    "company": "Northwind Dental",
    "board": "Projects",
    "status": "Scheduled",
    "created_at": "2026-11-05T09:30:00Z"
  }

• update_ticket Change status, priority, type, subtype, item, owner or board of a ticket. writeasks first

  Changes only the fields you pass and returns the ticket as it is afterwards. When the board changes, PSA keeps status, type, subtype and item if they exist on the new board. A status change can run the rules of that board, such as closing, so each call waits for your OK. By default you confirm each call; you can switch that off for this tool.

  MCP callconnectwise_write → update_ticket

  REST endpointPATCH https://cotlet.dev/api/v1/connectwise/tickets/{ticket_id}

  Parameters

  Parameters: update_ticket

  Name	Type	Description
  ticket_id integer required	integer	Ticket number from list_tickets or get_ticket.
  status string	string	Status name on the ticket board.
  priority string	string	Priority name as shown on the ticket.
  type string	string	Type from list_service_boards.
  subtype string	string	Subtype from list_service_boards.
  item string	string	Item from list_service_boards.
  owner string	string	Member identifier of the new owner.
  board string	string	Move the ticket to this board.

  Example input

  {
    "ticket_id": 1
  }

  Example response

  {
    "ticket_id": 30412,
    "board": "Service Desk",
    "status": "In Progress",
    "priority": "Priority 2 - High",
    "type": "Incident",
    "owner": "mreyes",
    "updated_at": "2026-11-05T09:12:00Z"
  }

ToolWhat it doesAccess

• list_ticket_notes Read the notes of a ticket, oldest first. read

  Returns notes oldest first, so the thread reads in order, with author, date and which tab each note sits on. PSA keeps Discussion, Internal and Resolution notes on separate tabs, and a ticket holds up to 1000 notes in total. Discussion notes are the ones customers can receive.

  MCP callconnectwise_read → list_ticket_notes

  REST endpointGET https://cotlet.dev/api/v1/connectwise/ticket-notes

  Parameters

  Parameters: list_ticket_notes

  Name	Type	Description
  ticket_id integer required	integer	Ticket number from list_tickets or get_ticket.
  note_type string	string	all, discussion, internal or resolution. Default all.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "ticket_id": 1
  }

  Example response

  {
    "ticket_id": 30412,
    "notes": [
      {
        "note_id": 884102,
        "note_type": "discussion",
        "author": "Dana Whitfield",
        "created_at": "2026-11-05T08:41:00Z",
        "text": "Nothing prints since 8 am. Three people are waiting."
      },
      {
        "note_id": 884119,
        "note_type": "internal",
        "author": "Maria Reyes",
        "created_at": "2026-11-05T09:05:00Z",
        "text": "Spooler service stopped on the print server. Restarting after lunch."
      }
    ],
    "next_cursor": null
  }

• add_ticket_note Add a Discussion, Internal or Resolution note to a ticket. writeasks first

  Adds the note to the tab you name and returns its id. In PSA, Discussion notes go to external and internal contacts, while Internal and Resolution notes go only to internal contacts. A ticket holds up to 1000 notes in total, and a note cannot be removed by this tool. By default you confirm each call; you can switch that off for this tool.

  MCP callconnectwise_write → add_ticket_note

  REST endpointPOST https://cotlet.dev/api/v1/connectwise/tickets/{ticket_id}/note

  Parameters

  Parameters: add_ticket_note

  Name	Type	Description
  ticket_id integer required	integer	Ticket number from list_tickets or get_ticket.
  note_type string required	string	discussion, internal or resolution.
  text string required	string	The note text.

  Example input

  {
    "ticket_id": 30412,
    "note_type": "discussion",
    "text": "Hi Dana, the print service stopped on the server. We restart it at 1 pm and will confirm here when printing works."
  }

  Example response

  {
    "ticket_id": 30412,
    "note_id": 884140,
    "note_type": "discussion",
    "created_at": "2026-11-05T09:20:00Z"
  }

ToolWhat it doesAccess

• list_time_entries List time entries by ticket, member or date range. read

  Returns one row per time entry with ticket, member, date, hours, work type, work role and the billable option. Use it before add_time_entry to see whether a ticket already has time. Give at least one of ticket_id, member or a date range, so the result stays small.

  MCP callconnectwise_read → list_time_entries

  REST endpointGET https://cotlet.dev/api/v1/connectwise/time-entries

  Parameters

  Parameters: list_time_entries

  Name	Type	Description
  ticket_id integer	integer	Only entries on this ticket.
  member string	string	Member identifier of who logged the time.
  date_from string	string	ISO date, first day included.
  date_to string	string	ISO date, last day included.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "entries": [
      {
        "time_entry_id": 55120,
        "ticket_id": 30398,
        "member": "mreyes",
        "date": "2026-11-04",
        "hours": 1.5,
        "work_type": "Remote",
        "work_role": "Service Desk",
        "billable_option": "Billable"
      },
      {
        "time_entry_id": 55131,
        "ticket_id": 30398,
        "member": "mreyes",
        "date": "2026-11-04",
        "hours": 0.5,
        "work_type": "Remote",
        "work_role": "Service Desk",
        "billable_option": "Billable"
      }
    ],
    "next_cursor": null
  }

• add_time_entry Log time on a ticket. writeasks first

  Creates the time entry for the signed-in member and returns it. Work type and work role change the rate that is billed, so the agent leaves them out unless you name them. Time feeds invoices, so each call waits for your OK. By default you confirm each call; you can switch that off for this tool.

  MCP callconnectwise_write → add_time_entry

  REST endpointPOST https://cotlet.dev/api/v1/connectwise/tickets/{ticket_id}/time-entries

  Parameters

  Parameters: add_time_entry

  Name	Type	Description
  ticket_id integer required	integer	Ticket number from list_tickets or get_ticket.
  hours number required	number	Hours worked, for example 1.5.
  date string	string	ISO date of the work. Today when left out.
  work_type string	string	Work type as named in PSA.
  work_role string	string	Work role as named in PSA.
  billable_option string	string	Billable, Do Not Bill or No Charge, as on the time entry screen.
  notes string	string	Note of the time entry.

  Example input

  {
    "ticket_id": 1,
    "hours": 1
  }

  Example response

  {
    "time_entry_id": 55162,
    "ticket_id": 30412,
    "member": "mreyes",
    "date": "2026-11-05",
    "hours": 1.5,
    "work_type": "Remote",
    "billable_option": "Billable"
  }

ToolWhat it doesAccess

• search_companies Find companies by name or identifier. read

  Returns the company identifier, name and status of each match. Use the identifier in create_ticket and list_tickets. A name that matches several companies returns all of them, and the agent asks you which one you mean.

  MCP callconnectwise_read → search_companies

  REST endpointGET https://cotlet.dev/api/v1/connectwise/companies/search

  Parameters

  Parameters: search_companies

  Name	Type	Description
  query string required	string	Part of the company name or its identifier.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "query": "query"
  }

  Example response

  {
    "companies": [
      {
        "company_id": "NorthwindDental",
        "name": "Northwind Dental",
        "status": "Active"
      },
      {
        "company_id": "NorthwindVet",
        "name": "Northwind Veterinary",
        "status": "Active"
      }
    ],
    "next_cursor": null
  }