Autotask

Link a ticket to a service call. This associates the ticket with the service call for scheduling purposes.

Assign a resource (technician) to a service call ticket.

Create a new task in Autotask

Create new ticket record

Upload a file attachment to an existing ticket. The file content must be passed as a base64-encoded string in the `data` field (MCP is JSON-RPC, so binary bytes must be base64-encoded). Autotask enforces a 3 MB hard limit on ticket attachments; this tool validates the decoded size before calling the API and returns a clear error if the limit is exceeded. Example: { ticketId: 12345, title: "screenshot.png", data: "iVBORw0KGgoAAAANSUhEUgAA..." }

Create charge on ticket for materials, costs, or expenses.

Add a new checklist item to a ticket.

Create a new note for a ticket

Create a time entry in Autotask. Can be tied to a ticket or task, OR created as "Regular Time" (no parent) for meetings, admin work, etc. For Regular Time, specify a category like "Internal Meeting", "Office Management", "Training", etc.

⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a quote item (line item) from a quote. This action cannot be undone. Confirm with the user before invoking.

⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a service call and all associated data. This action cannot be undone. Confirm with the user before invoking.

⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently removes a ticket association from a service call. This action cannot be undone. Confirm with the user before invoking.

⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently removes a resource assignment from a service call ticket. This action cannot be undone. Confirm with the user before invoking.

⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a ticket charge record and all associated billing data. This action cannot be undone. Confirm with the user before invoking.

⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a checklist item from a ticket. This action cannot be undone. Confirm with the user before invoking.

Execute any Autotask tool by name. Use after discovering tools via autotask_list_category_tools.

Get detailed information for a specific billing item by ID

Get a specific company note by company ID and note ID

Get company site configuration records. Call first to discover available fields.

Get a single contract by ID (header fields only, no service lines)

Recurring-revenue roll-up for one contract: every service and bundle line with units active on a day, joined to the catalog (service name, vendor, billing period) and normalized to a monthly total. Returns { contractID, contractName, companyID, companyName, activeOn, lines[], monthlyTotal, monthlyCost, unresolvedPeriodTypes[] }. Use this for MRR, licensing reconciliation, and "what does this client pay for" questions. Read-only.

Get a specific expense report by ID

Get field definitions for an Autotask entity type, including picklist values. Useful for discovering valid values for any picklist field.

Get a single Autotask invoice with its nested line items (billing items posted to the invoice). Use for finance workflows that need to see exactly what an invoice contains.

Get a specific opportunity by ID

Get a specific product by ID

Get a specific project note by project ID and note ID

Get a specific quote by ID

Get a specific quote item by ID

Get a specific service by ID

Get a specific service bundle by ID

Get a specific service call by ID

Get a ticket attachment. With includeData=false (default) returns metadata only — fast, suitable for browsing. With includeData=true returns the base64 binary content via the top-level /TicketAttachments/{id} endpoint (the child endpoint never populates data). The attachment is verified to belong to the given ticketId. Oversized binaries are stripped from the response with a dataOmittedReason field — Autotask attachments can be up to 3 MB, which is ~4 MB as base64 and may exceed the MCP client tool-result limit (~1 MB).

Get a specific ticket charge by ID

Get a ticket's details: description, status, priority, queue, company, assignee, dates, linked configuration item, resolution and recent notes. Set fullDetails:true for untruncated description/resolution and custom (UDF) fields.

Get a single ticket history entry by ID. Each entry records one audited change to a ticket field (who, when, before/after).

Get a specific ticket note by ticket ID and note ID

Get an uploaded file attachment on a ticket note (distinct from attachments on the ticket itself). With includeData=false (default) returns metadata only — any file bytes Autotask included are omitted. With includeData=true returns the base64 file bytes from GET /TicketNotes/{ticketNoteId}/Attachments/{attachmentId}, which is parent-scoped and is the call that populates data for note attachments. If that response omits data, falls back to GET /TicketNoteAttachments/{id} and uses those bytes only when ticketNoteID or parentID matches the note; if the bytes cannot be verified, returns an error i…

List available tool categories. Use this to discover what types of Autotask operations are available before loading specific tools.

List tools in a specific category with full schemas. Use after autotask_list_categories to see available tools and their parameters.

List contracts whose end date falls within the next N days (expiring-contracts report). Optionally include already-expired contracts, and scope to one company or the whole org.

List phases for a project in Autotask

List all available ticket queues in Autotask. Use this to find queue IDs for filtering tickets by queue.

List all available ticket priorities in Autotask. Use this to find priority values for filtering or creating tickets.

List all available ticket statuses in Autotask. Use this to find status values for filtering or creating tickets.

Escape hatch for Autotask REST endpoints not yet wrapped by a typed tool. Prefer typed tools. The path is relative to the zone v1.0 base (https://webservices<N>.autotask.net/ATServicesRest/v1.0) and must not start with /v1.0. Searches are POST /{Entity}/query with a body of {"filter":[...]}. Example: POST /Companies/query {"filter":[{"op":"eq","field":"id","value":175}]}. Auth headers are added automatically. queryParams is a flat object of string/number/boolean values appended to the path.

Intelligent tool router - describe what you want to do and get the right tool suggestion with pre-filled parameters. Use this when unsure which tool to call.

Search for billing item approval levels. These describe multi-level approval records for Autotask time entries, enabling visibility into tiered approval workflows.

Search for billing items in Autotask. Billing items represent approved and posted billable items from the "Approve and Post" workflow. Returns 25 results per page by default.

Search companies by name or status. Max 200/page.

Search for notes on a specific company. Iterating across many companies trips Autotask's API threshold — scope the parent list first.

Search for configuration items in Autotask with optional filters

Search contacts by name, email, or company. Max 200/page.

Billed unit rows for bundle lines on a contract (ContractServiceBundleUnits), active on a given day (default today). Read-only.

List the service-bundle line items on a contract (ContractServiceBundles). Read-only.

Billed unit rows for a contract (ContractServiceUnits): the quantity and contract price of each service line over a date range. By default returns only rows active today, i.e. what is currently being invoiced. Read-only.

List the service line items on a contract (ContractServices): which catalog services are on the contract and at what contract-specific unit price. Read-only. Pair with autotask_search_contract_service_units for billed quantities, or use autotask_get_contract_recurring_lines for both in one call.

Search for contracts in Autotask with optional filters

Search for expense reports with optional filters

Search for invoices in Autotask with optional filters

Search for opportunities with optional filters

Search for products with optional filters

Search for notes on a specific project. Fan-out across many projects trips Autotask's API threshold (see issue #69) — scope the parent list (status, company, date range) first.

Search for projects in Autotask. Returns 25 results per page by default. Use page parameter for more results.

Search for quote items, typically filtered by quote ID

Search for quotes with optional filters

List the billing roles a resource (user) holds in Autotask, with names and role IDs. A ticket assigned to a resource and every ticket/task time entry need one of these role IDs; this is where to find them instead of guessing. Give resourceId or resourceName. Active roles only unless includeInactive is true.

Search for resources (users) in Autotask. Returns 25 results per page by default. Use page parameter for more results.

Search for service bundles with optional filters

Search for resource (technician) assignments on service call tickets.

Search for ticket associations on service calls. Use this to find which tickets are linked to a service call, or which service calls contain a specific ticket.

Search for service calls in Autotask. Filter by company, status, or date range.

Search for services with optional filters

Search for tasks in Autotask. Returns 25 results per page by default. Use page parameter for more results.

Search for attachments on a specific ticket. Each parent triggers a separate query — scope the parent ticket list before iterating.

Search ticket charges (materials, costs, expenses). Provide ticketId for best performance. Max 10 if unfiltered.

List all checklist items on a ticket, including their completion status. Checklist items are a sub-resource of a ticket and cannot be queried without a ticket ID.

Get the audit trail of field changes for a ticket (status transitions, assignment changes, priority edits, etc.). Use this to answer questions like "when did this ticket move from In Progress to Waiting Customer" or "who changed the priority". Returns entries ordered by Autotask; sort/filter client-side if needed.

Search for attachments on a specific ticket note — use this when autotask_search_ticket_notes returns a note with an empty or unhelpful `description`, since the real content is often a pasted image or file living on the note rather than in its text. Each note triggers a separate query — scope the parent note list before iterating.

Search for notes on a specific ticket. Iterating across many tickets trips Autotask's per-integration API threshold — scope the parent list first.

Search tickets by company, queue, status, priority. Use autotask_get_ticket_details for full data. Max 500/page.

Search for time entries in Autotask. Returns 25 results per page by default. Time entries can be filtered by resource, ticket, task, date range, or approval status. Use approvalStatus="unapproved" to find entries not yet posted. Each entry includes summaryNotes and internalNotes. There is no project filter — Autotask time entries have no project field; to get a project's time, call autotask_search_tasks with that projectID and filter by the returned taskId values. Common fan-out target — scope by date range first to avoid Autotask's API threshold.

Test Autotask API connection

Update company record. invoiceTemplateID sets payment terms (103=Due on Receipt, 104=NET 30). Billing address fields separate from regular address.

Update company site configuration. Fields are tenant-defined; call get first.

Update contact record. Only provided fields are changed.

Update an existing Contract in Autotask (PATCH). Pass only fields you want to change; everything except id is optional. status: 1=In Effect, 0=Inactive.

Update an existing ContractService line on a Contract. Pass only fields you want to change.

Update an existing opportunity in Autotask. Only the fields you provide will be updated. Autotask derives amount (total revenue) and cost from the per-period fields (onetimeRevenue, monthlyRevenue, onetimeCost, monthlyCost, etc.), so change revenue and cost through those. Setting amount or cost directly replaces the whole breakdown: the total becomes one-time and any recurring revenue or cost is cleared. Setting useQuoteTotals=true replaces revenue and cost with the primary quote's totals.

Update an existing project in Autotask. Only the fields you provide will be updated. Common use case: set status=5 to mark a project Complete.

Update an existing quote item (quantity, price, etc.)

Update an existing service call. Use this to change status, times, or description. To complete/close a service call, set complete: true or update the status.

Update ticket record. Only provided fields are changed.

Update an existing ticket charge. Only fields provided will be changed.

Update a checklist item on a ticket — edit text, mark complete/incomplete, or change position.