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

ToolWhat it doesAccess

• search_tickets Find tickets by company, status, queue, priority, assignee or age. read

  Returns tickets with number, title, company, status, priority, queue, assignee, created and last activity date. Results come in pages: follow next_cursor until it is empty. You see the tickets your Autotask security level lets you see.

  MCP callautotask_read → search_tickets

  REST endpointGET https://cotlet.dev/api/v1/autotask/tickets/search

  Parameters

  Parameters: search_tickets

  Name	Type	Description
  query string	string	Text to look for in the ticket title.
  company_id integer	integer	Company ID from search_companies.
  status string	string	Status label as Autotask shows it; labels from list_ticket_options.
  queue string	string	Queue label; labels from list_ticket_options.
  priority string	string	Priority label; labels from list_ticket_options.
  assigned_to string	string	A resource name, "me" for your own tickets, or "unassigned".
  updated_before string	string	ISO date. Only tickets with no update since then.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "tickets": [
      {
        "ticket_id": 48213,
        "number": "T20261104.0007",
        "title": "Printer offline on reception",
        "company": "Acme Dental",
        "status": "New",
        "priority": "Medium",
        "queue": "Service Desk",
        "assignee": null,
        "created": "2026-11-04",
        "last_activity": "2026-11-04"
      },
      {
        "ticket_id": 48190,
        "number": "T20261103.0011",
        "title": "Cannot open shared drive",
        "company": "Brightwell Legal",
        "status": "In Progress",
        "priority": "High",
        "queue": "Service Desk",
        "assignee": "Sam Okafor",
        "created": "2026-11-03",
        "last_activity": "2026-11-05"
      }
    ],
    "next_cursor": null
  }

• get_ticket Read one ticket with its description, contact and fields. read

  Returns the title, description, company, contact, status, priority, queue, assignee, due date and the ticket fields as Autotask shows them. Notes and time entries come from list_ticket_notes and list_time_entries.

  MCP callautotask_read → get_ticket

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

  Parameters

  Parameters: get_ticket

  Name	Type	Description
  ticket_id integer required	integer	Ticket ID from search_tickets.

  Example input

  {
    "ticket_id": 1
  }

  Example response

  {
    "ticket_id": 48213,
    "number": "T20261104.0007",
    "title": "Printer offline on reception",
    "description": "The reception printer shows offline since this morning. Restarting did not help.",
    "company": "Acme Dental",
    "contact": "Lena Ortiz",
    "status": "New",
    "priority": "Medium",
    "queue": "Service Desk",
    "assignee": null,
    "due": "2026-11-06"
  }

• list_ticket_options List the statuses, priorities and queues your Autotask account uses. read

  Returns the labels as your Autotask account shows them, so your agent uses your own names and not a guess. Call it before update_ticket or create_ticket.

  MCP callautotask_read → list_ticket_options

  REST endpointGET https://cotlet.dev/api/v1/autotask/ticket-options

  Parameters

  No parameters.

  Example response

  {
    "statuses": [
      "New",
      "In Progress",
      "Waiting Customer",
      "Complete"
    ],
    "priorities": [
      "Low",
      "Medium",
      "High",
      "Critical"
    ],
    "queues": [
      "Service Desk",
      "Projects",
      "Triage"
    ]
  }

• create_ticket Open a new ticket for a company. writeasks first

  Creates the ticket as you and returns its ID and number. Autotask then runs its own rules for new tickets, such as workflow rules and notifications to the contact. By default you confirm each call; you can switch that off for this tool.

  MCP callautotask_write → create_ticket

  REST endpointPOST https://cotlet.dev/api/v1/autotask/companies/{company_id}/tickets

  Parameters

  Parameters: create_ticket

  Name	Type	Description
  company_id integer required	integer	Company ID from search_companies.
  title string required	string	Ticket title.
  description string	string	What the customer reported.
  contact_id integer	integer	Contact ID from search_contacts.
  priority string	string	Priority label from list_ticket_options.
  queue string	string	Queue label from list_ticket_options.

  Example input

  {
    "company_id": 1,
    "title": "title"
  }

  Example response

  {
    "ticket_id": 48230,
    "number": "T20261106.0003",
    "status": "New",
    "url": "https://ww5.autotask.net/Mvc/ServiceDesk/TicketDetail.mvc?ticketId=48230"
  }

• update_ticket Change status, priority, queue or assignee of a ticket. writeasks first

  Changes only the fields you pass and returns the ticket as it is now. A label that Autotask does not have fails at once and the error lists the valid ones. Autotask rules and notifications can react to the change, for example to the assignee. By default you confirm each call; you can switch that off for this tool.

  MCP callautotask_write → update_ticket

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

  Parameters

  Parameters: update_ticket

  Name	Type	Description
  ticket_id integer required	integer	Ticket ID from search_tickets.
  status string	string	Status label from list_ticket_options.
  priority string	string	Priority label from list_ticket_options.
  queue string	string	Queue label from list_ticket_options.
  assignee string	string	A resource name.

  Example input

  {
    "ticket_id": 1
  }

  Example response

  {
    "ticket_id": 48213,
    "status": "In Progress",
    "priority": "High",
    "queue": "Service Desk",
    "assignee": "Sam Okafor"
  }

ToolWhat it doesAccess

• list_ticket_notes Read the notes on a ticket, newest first. read

  Returns each note with its title, text, author, date and publish setting. Newest first. Follow next_cursor for older notes.

  MCP callautotask_read → list_ticket_notes

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

  Parameters

  Parameters: list_ticket_notes

  Name	Type	Description
  ticket_id integer required	integer	Ticket ID from search_tickets.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "ticket_id": 1
  }

  Example response

  {
    "notes": [
      {
        "note_id": 90417,
        "title": "Status update",
        "body": "Driver reinstalled. Waiting for the client to test a print.",
        "author": "Sam Okafor",
        "created": "2026-11-05",
        "publish": "Internal"
      }
    ],
    "next_cursor": null
  }

• add_ticket_note Add a note to a ticket. writeasks first

  Saves the note on the ticket and returns its ID and the publish setting Autotask applied. A note can reach the customer or the technician through Autotask notifications. By default you confirm each call; you can switch that off for this tool.

  MCP callautotask_write → add_ticket_note

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

  Parameters

  Parameters: add_ticket_note

  Name	Type	Description
  ticket_id integer required	integer	Ticket ID from search_tickets.
  body string required	string	Note text.
  title string	string	Note title.

  Example input

  {
    "ticket_id": 48213,
    "title": "Triage",
    "body": "Looks like a driver issue after the update. Moving to Service Desk, priority High."
  }

  Example response

  {
    "note_id": 90431,
    "ticket_id": 48213,
    "title": "Triage",
    "publish": "Internal",
    "created": "2026-11-06"
  }

ToolWhat it doesAccess

• list_time_entries Read the time entries logged on a ticket or by a person on a day. read

  Returns each entry with ticket, person, date, hours and summary. It adds up the hours per ticket in total_hours. You see the entries your Autotask security level lets you see.

  MCP callautotask_read → list_time_entries

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

  Parameters

  Parameters: list_time_entries

  Name	Type	Description
  ticket_id integer	integer	Ticket ID from search_tickets. Leave out to read by person and date.
  resource string	string	A resource name or "me". Used with date.
  date string	string	ISO date for the entries of one day.
  cursor string	string	Next page cursor from the previous call.

  Example response

  {
    "entries": [
      {
        "entry_id": 77120,
        "ticket_id": 48190,
        "resource": "Sam Okafor",
        "date": "2026-11-05",
        "hours": 1.5,
        "summary": "Remapped the shared drive"
      },
      {
        "entry_id": 77096,
        "ticket_id": 48190,
        "resource": "Sam Okafor",
        "date": "2026-11-04",
        "hours": 0.5,
        "summary": "First check"
      }
    ],
    "total_hours": 2,
    "next_cursor": null
  }

• log_time_entry Log hours on a ticket. writeasks first

  Adds the entry under your own resource and returns it. Time is billable money, so it asks for your OK. Autotask can refuse time on a Complete ticket when its Service Desk setting prohibits it, and the error says so. By default you confirm each call; you can switch that off for this tool.

  MCP callautotask_write → log_time_entry

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

  Parameters

  Parameters: log_time_entry

  Name	Type	Description
  ticket_id integer required	integer	Ticket ID from search_tickets.
  hours number required	number	Hours worked, for example 0.5.
  summary string required	string	What was done.
  date string	string	ISO date. Defaults to today.

  Example input

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

  Example response

  {
    "entry_id": 77131,
    "ticket_id": 48190,
    "resource": "Sam Okafor",
    "date": "2026-11-06",
    "hours": 0.5,
    "summary": "Checked the shared drive mapping"
  }

ToolWhat it doesAccess

• search_companies Find companies (accounts) by name. read

  Returns the company ID, name, phone and whether it is active. Use the ID in search_tickets, search_contacts and create_ticket.

  MCP callautotask_read → search_companies

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

  Parameters

  Parameters: search_companies

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

  Example input

  {
    "query": "query"
  }

  Example response

  {
    "companies": [
      {
        "company_id": 1182,
        "name": "Acme Dental",
        "phone": "+1 555 0142",
        "active": true
      }
    ],
    "next_cursor": null
  }

• search_contacts Find the people at a company by name or email. read

  Returns the contact ID, name, email and phone. Use the contact ID in create_ticket.

  MCP callautotask_read → search_contacts

  REST endpointGET https://cotlet.dev/api/v1/autotask/companies/{company_id}/contacts/search

  Parameters

  Parameters: search_contacts

  Name	Type	Description
  company_id integer required	integer	Company ID from search_companies.
  query string	string	Part of the name or email.
  cursor string	string	Next page cursor from the previous call.

  Example input

  {
    "company_id": 1
  }

  Example response

  {
    "contacts": [
      {
        "contact_id": 5531,
        "name": "Lena Ortiz",
        "email": "lena@example.com",
        "phone": "+1 555 0143"
      }
    ],
    "next_cursor": null
  }