Test Autotask API connection

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

Create new company record

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

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

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

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

Create new contact record

Update contact record. Only provided fields are changed.

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

Get full ticket details including notes, time entries, and custom fields.

Create new ticket record

Update ticket record. Only provided fields are changed.

Get a specific ticket charge by ID

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

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

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

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

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

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.

Create a time entry in Autotask. Can be tied to a ticket, task, or project, 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.

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

Create a new project in Autotask

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.

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

Get a specific ticket note by ticket ID and note ID

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

Create a new note for a ticket

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.

Add a new checklist item to a ticket.

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

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

Get a specific project note by project ID and note ID

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.

Create a new note for a project

Get a specific company note by company ID and note ID

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

Create a new note for a company

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).

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

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..." }

Get a specific expense report by ID

Search for expense reports with optional filters

Create a new expense report

Create an expense item on an existing expense report

Get a specific quote by ID

Search for quotes with optional filters

Create a new quote

Get a specific opportunity by ID

Search for opportunities with optional filters

Create a new sales opportunity in Autotask

Get a specific product by ID

Search for products with optional filters

Get a specific service by ID

Search for services with optional filters

Get a specific service bundle by ID

Search for service bundles with optional filters

Get a specific quote item by ID

Search for quote items, typically filtered by quote ID

Create a line item on a quote. Set exactly ONE item reference (serviceID, productID, or serviceBundleID). Required: quoteId, quantity. Defaults: unitDiscount=0, lineDiscount=0, percentageDiscount=0, isOptional=false.

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

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

Search for configuration items in Autotask with optional filters

Search for contracts in Autotask with optional filters

Search for invoices in Autotask with optional filters

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.

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

Create a new task in Autotask

List phases for a project in Autotask

Create a new phase in an Autotask project

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

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

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

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

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.

Get detailed information for a specific billing item by ID

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

Search for time entries in Autotask. Returns 25 results per page by default. Time entries can be filtered by resource, ticket, project, task, date range, or approval status. Use approvalStatus="unapproved" to find entries not yet posted. Common fan-out target — scope by date range first to avoid Autotask's API threshold.

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.

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

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.

Get a specific service call by ID

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

Create a new service call in Autotask. Service calls are used to schedule and plan work on tickets.

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.

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

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.

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

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

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

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

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

Create a new Contract in Autotask. Field names match the Autotask REST API exactly. status: 1=In Effect, 0=Inactive. Dates are ISO format (YYYY-MM-DD).

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.

Add a ContractService (service line item) to an existing Contract.

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

Escape hatch for Autotask REST endpoints not yet wrapped by a typed tool. Use sparingly — typed tools are preferred for safety. The existing Content-Type, Accept, ApiIntegrationcode, UserName, Secret headers are added automatically. The path is resolved against the zone-resolved base URL (https://webservices.autotask.net/ATServicesRest/v1.0). Pass queryParams as a flat object of string/number/boolean values; they will be URL-encoded and appended to the path.