Autotask
OCI · GHCR.IO/WYRE-TECHNOLOGY/AUTOTASK-MCP:V2.32.10
MCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.
Available components
Last scanned (23 hours ago)
Scores higher than 73% of OCI servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 56 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 13091 tokens (~120/item across 109 items; 101 tools + 8 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety90
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 6 of 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "autotask_get_ticket_charge" implies "charge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 103 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −2
No change was recorded against any check on this day. Stability & Change Management went from 97 to 80.
- 10 Oct 26 −1
- Stability: pass → 0.97 functional
- 4 Oct 26 +1
- Stability: 0.97 → pass security
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Analysed oci/ghcr.io/wyre-technology/autotask-mcp:v2.32.10
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
autotask_get_ticket_note ~47
Get a specific ticket note by ticket ID and note ID
| Name | Type | Req | Description |
|---|---|---|---|
| noteId | number | yes | The note ID to retrieve |
| ticketId | number | yes | The ticket ID |
No output schema declared.
No examples provided.
autotask_list_categories ~33
List available tool categories. Use this to discover what types of Autotask operations are available before loading specific tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
autotask_list_category_tools ~61
List tools in a specific category with full schemas. Use after autotask_list_categories to see available tools and their parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category name from autotask_list_categories (e.g., "tickets", "financial", "companies") |
No output schema declared.
No examples provided.
autotask_list_expiring_contracts ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| companyID | number | – | Limit the report to one company (omit for the whole org) |
| daysAhead | number | – | Look-ahead window in days (default: 60) |
| includeExpired | boolean | – | Also include contracts whose end date is already in the past (default: false) |
| pageSize | number | – | Number of results to return (default: 100, max: 500) |
| status | number | – | Filter by contract status (1=In Effect, 3=Terminated) |
No output schema declared.
No examples provided.
autotask_list_phases ~56
List phases for a project in Autotask
| Name | Type | Req | Description |
|---|---|---|---|
| pageSize | number | – | Results per page (default: 25, max: 100) |
| projectID | number | yes | Project ID to list phases for |
No output schema declared.
No examples provided.
autotask_list_queues ~33
List all available ticket queues in Autotask. Use this to find queue IDs for filtering tickets by queue.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
autotask_list_ticket_priorities ~34
List all available ticket priorities in Autotask. Use this to find priority values for filtering or creating tickets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
autotask_list_ticket_statuses ~34
List all available ticket statuses in Autotask. Use this to find status values for filtering or creating tickets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
autotask_raw_request ~197
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<N>.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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | Optional JSON body for POST/PATCH requests |
| method | string | yes | HTTP method |
| path | string | yes | Path under the Autotask REST v1.0 base (e.g. "/Companies/175" or "/Companies/query") |
| queryParams | object | – | Optional flat key-value query parameters (e.g. { includeFields: "id,name" }) |
No output schema declared.
No examples provided.
autotask_router ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| intent | string | yes | Natural language description of what you want to do (e.g., "find tickets for Acme Corp", "log 2 hours on ticket 12345", "create a quote for client") |
No output schema declared.
No examples provided.
autotask_search_billing_item_approval_levels ~148
Search for billing item approval levels. These describe multi-level approval records for Autotask time entries, enabling visibility into tiered approval workflows.
| Name | Type | Req | Description |
|---|---|---|---|
| approvalLevel | number | – | Filter by approval level (1, 2, 3, etc.) |
| approvalResourceId | number | – | Filter by approver resource ID |
| approvedAfter | string | – | Filter approvals on or after this date (ISO format) |
| approvedBefore | string | – | Filter approvals on or before this date (ISO format) |
| page | number | – | – |
| pageSize | number | – | Max 500 |
| timeEntryId | number | – | Filter by time entry ID |
No output schema declared.
No examples provided.
autotask_search_billing_items ~284
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.
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | number | – | Filter by company ID |
| contractId | number | – | Filter by contract ID |
| dateFrom | string | – | Filter billing items with itemDate on or after this date (ISO format, e.g. 2026-01-01) |
| dateTo | string | – | Filter billing items with itemDate on or before this date (ISO format) |
| invoiceId | number | – | Filter by invoice ID |
| isInvoiced | boolean | – | If true, only return billing items that have been attached to an invoice (invoiceID is set). If false, only return items that have not yet been invoiced. Answers "what has and hasn't been invoiced ye… |
| page | number | – | – |
| pageSize | number | – | Max 500 |
| postedAfter | string | – | Filter items posted on or after this date (ISO format, e.g. 2026-01-01) |
| postedBefore | string | – | Filter items posted on or before this date (ISO format) |
| projectId | number | – | Filter by project ID |
| ticketId | number | – | Filter by ticket ID |
No output schema declared.
No examples provided.
autotask_search_companies ~57
Search companies by name or status. Max 200/page.
| Name | Type | Req | Description |
|---|---|---|---|
| isActive | boolean | – | – |
| page | number | – | – |
| pageSize | number | – | Max 200 |
| searchTerm | string | – | – |
No output schema declared.
No examples provided.
autotask_search_company_notes ~76
Search for notes on a specific company. Iterating across many companies trips Autotask's API threshold — scope the parent list first.
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | number | yes | The company ID to search notes for |
| pageSize | number | – | Number of results to return (default: 25, max: 100) |
No output schema declared.
No examples provided.
autotask_search_configuration_items ~127
Search for configuration items in Autotask with optional filters
| Name | Type | Req | Description |
|---|---|---|---|
| companyID | number | – | Filter by company ID |
| configurationItemCategoryID | number | – | Filter by configuration item category ID |
| configurationItemType | number | – | Filter by configuration item type (numeric picklist value) |
| isActive | boolean | – | – |
| pageSize | number | – | Number of results to return (default: 25, max: 500) |
| productID | number | – | Filter by product ID |
| searchTerm | string | – | Search term for configuration item name |
No output schema declared.
No examples provided.
autotask_search_contacts ~91
Search contacts by name, email, or company. Max 200/page.
| Name | Type | Req | Description |
|---|---|---|---|
| companyID | number | – | Filter by company ID |
| isActive | number | – | Filter by active status (1=active, 0=inactive) |
| page | number | – | – |
| pageSize | number | – | Max 200 |
| searchTerm | string | – | Search term for contact name or email |
No output schema declared.
No examples provided.
autotask_search_contracts ~151
Search for contracts in Autotask with optional filters
| Name | Type | Req | Description |
|---|---|---|---|
| companyID | number | – | Filter by company ID |
| contractType | number | – | Filter by contract type picklist ID |
| endDateFrom | string | – | Only contracts ending on or after this date (ISO YYYY-MM-DD) |
| endDateTo | string | – | Only contracts ending on or before this date (ISO YYYY-MM-DD) |
| pageSize | number | – | Number of results to return (default: 25, max: 500) |
| searchTerm | string | – | Search term for contract name |
| status | number | – | Filter by contract status (1=In Effect, 3=Terminated) |
No output schema declared.
No examples provided.
autotask_search_expense_reports ~98
Search for expense reports with optional filters
| Name | Type | Req | Description |
|---|---|---|---|
| pageSize | number | – | Number of results to return (default: 25, max: 100) |
| status | number | – | Filter by status (1=New, 2=Submitted, 3=Approved, 4=Paid, 5=Rejected, 6=InReview) |
| submitterId | number | – | Filter by submitter resource ID |
No output schema declared.
No examples provided.
autotask_search_invoices ~83
Search for invoices in Autotask with optional filters
| Name | Type | Req | Description |
|---|---|---|---|
| companyID | number | – | Filter by company ID |
| invoiceNumber | string | – | Filter by invoice number |
| isVoided | boolean | – | Filter by voided status |
| pageSize | number | – | Number of results to return (default: 25, max: 500) |
No output schema declared.
No examples provided.
autotask_search_opportunities ~76
Search for opportunities with optional filters
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | number | – | Filter by company ID |
| pageSize | number | – | Number of results to return (default: 25, max: 100) |
| searchTerm | string | – | Search term for opportunity title |
| status | number | – | Filter by status |
No output schema declared.
No examples provided.
autotask_search_products ~61
Search for products with optional filters
| Name | Type | Req | Description |
|---|---|---|---|
| isActive | boolean | – | – |
| pageSize | number | – | Number of results to return (default: 25, max: 100) |
| searchTerm | string | – | Search term for product name |
No output schema declared.
No examples provided.
autotask_search_project_notes ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pageSize | number | – | Number of results to return (default: 25, max: 100) |
| projectId | number | yes | The project ID to search notes for |
No output schema declared.
No examples provided.
autotask_search_projects ~114
Search for projects in Autotask. Returns 25 results per page by default. Use page parameter for more results.
| Name | Type | Req | Description |
|---|---|---|---|
| companyID | number | – | Filter by company ID |
| page | number | – | – |
| pageSize | number | – | Results per page (default: 25, max: 100) |
| projectLeadResourceID | number | – | Filter by project lead resource ID |
| searchTerm | string | – | Search term for project name |
| status | number | – | Filter by project status |
No output schema declared.
No examples provided.
autotask_search_quote_items ~73
Search for quote items, typically filtered by quote ID
| Name | Type | Req | Description |
|---|---|---|---|
| pageSize | number | – | Number of results to return (default: 50, max: 100) |
| quoteId | number | – | Filter by quote ID (recommended) |
| searchTerm | string | – | Search term for quote item name |
No output schema declared.
No examples provided.
autotask_search_quotes ~91
Search for quotes with optional filters
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | number | – | Filter by company ID |
| contactId | number | – | Filter by contact ID |
| opportunityId | number | – | Filter by opportunity ID |
| pageSize | number | – | Number of results to return (default: 25, max: 100) |
| searchTerm | string | – | Search term for quote name or description |
No output schema declared.
No examples provided.
autotask_search_resources ~105
Search for resources (users) in Autotask. Returns 25 results per page by default. Use page parameter for more results.
| Name | Type | Req | Description |
|---|---|---|---|
| isActive | boolean | – | – |
| page | number | – | – |
| pageSize | number | – | Max 500 |
| resourceType | number | – | Filter by resource type (1=Employee, 2=Contractor, 3=Temporary) |
| searchTerm | string | – | Search term for resource name or email |
No output schema declared.
No examples provided.
autotask_search_service_bundles ~66
Search for service bundles with optional filters
| Name | Type | Req | Description |
|---|---|---|---|
| isActive | boolean | – | – |
| pageSize | number | – | Number of results to return (default: 25, max: 100) |
| searchTerm | string | – | Search term for service bundle name |
No output schema declared.
No examples provided.
autotask_search_service_call_ticket_resources ~76
Search for resource (technician) assignments on service call tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| pageSize | number | – | Number of results to return (default: 25) |
| resourceId | number | – | Filter by resource (technician) ID |
| serviceCallTicketId | number | – | Filter by service call ticket ID |
No output schema declared.
No examples provided.
autotask_search_service_call_tickets ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pageSize | number | – | Number of results to return (default: 25) |
| serviceCallId | number | – | Filter by service call ID |
| ticketId | number | – | Filter by ticket ID |
No output schema declared.
No examples provided.
autotask_search_service_calls ~144
Search for service calls in Autotask. Filter by company, status, or date range.
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | number | – | Filter by company ID |
| pageSize | number | – | Number of results to return (default: 25, max: 100) |
| startAfter | string | – | Filter service calls starting on or after this date/time (ISO 8601 format) |
| startBefore | string | – | Filter service calls starting on or before this date/time (ISO 8601 format) |
| status | number | – | Filter by status picklist ID (use autotask_get_field_info with entityType "ServiceCalls" to find valid values) |
No output schema declared.
No examples provided.
autotask_search_services ~61
Search for services with optional filters
| Name | Type | Req | Description |
|---|---|---|---|
| isActive | boolean | – | – |
| pageSize | number | – | Number of results to return (default: 25, max: 100) |
| searchTerm | string | – | Search term for service name |
No output schema declared.
No examples provided.
autotask_search_tasks ~127
Search for tasks in Autotask. Returns 25 results per page by default. Use page parameter for more results.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedResourceID | number | – | Filter by assigned resource ID |
| page | number | – | – |
| pageSize | number | – | Results per page (default: 25, max: 100) |
| projectID | number | – | Filter by project ID |
| searchTerm | string | – | Search term for task title |
| status | number | – | Filter by task status (1=New, 2=In Progress, 5=Complete) |
No output schema declared.
No examples provided.
autotask_search_ticket_attachments ~74
Search for attachments on a specific ticket. Each parent triggers a separate query — scope the parent ticket list before iterating.
| Name | Type | Req | Description |
|---|---|---|---|
| pageSize | number | – | Number of results to return (default: 10, max: 50) |
| ticketId | number | yes | The ticket ID to search attachments for |
No output schema declared.
No examples provided.
autotask_search_ticket_charges ~73
Search ticket charges (materials, costs, expenses). Provide ticketId for best performance. Max 10 if unfiltered.
| Name | Type | Req | Description |
|---|---|---|---|
| pageSize | number | – | Number of results to return (default: 25, max: 100) |
| ticketId | number | – | Filter by ticket ID (recommended) |
No output schema declared.
No examples provided.
autotask_search_ticket_checklist_items ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ticketId | number | yes | The ticket ID whose checklist items should be listed |
No output schema declared.
No examples provided.
autotask_search_ticket_history ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pageSize | number | – | Number of history entries to return (default: 50, max: 500) |
| ticketId | number | yes | The ticket ID to get history for (required — Autotask does not support unscoped history queries) |
No output schema declared.
No examples provided.
autotask_search_ticket_notes ~79
Search for notes on a specific ticket. Iterating across many tickets trips Autotask's per-integration API threshold — scope the parent list first.
| Name | Type | Req | Description |
|---|---|---|---|
| pageSize | number | – | Number of results to return (default: 25, max: 100) |
| ticketId | number | yes | The ticket ID to search notes for |
No output schema declared.
No examples provided.
autotask_search_tickets ~266
Search tickets by company, queue, status, priority. Use autotask_get_ticket_details for full data. Max 500/page.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedResourceID | number | – | Filter by assigned resource ID |
| companyID | number | – | Filter by company ID |
| contactID | number | – | Filter by primary contact ID — returns only tickets where contactID matches |
| createdAfter | string | – | Filter tickets created on or after this date (ISO format, e.g. 2026-01-01) |
| createdBefore | string | – | Filter tickets created on or before this date (ISO format) |
| lastActivityAfter | string | – | Filter tickets with activity on or after this date (ISO format) |
| page | number | – | – |
| pageSize | number | – | Max 500 |
| priority | number | – | Filter by ticket priority ID. Use autotask_list_ticket_priorities to discover valid IDs. |
| queueID | number | – | Filter by queue ID. Use autotask_list_queues to discover valid IDs. |
| searchTerm | string | – | Search by ticket number prefix |
| status | number | – | Filter by ticket status ID (omit for all open tickets) |
| unassigned | boolean | – | Set to true to find unassigned tickets |
No output schema declared.
No examples provided.
autotask_search_time_entries ~274
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.
| Name | Type | Req | Description |
|---|---|---|---|
| approvalStatus | string | – | Filter by approval status: "unapproved" = not yet posted (billingApprovalDateTime is null), "approved" = already posted, "all" = no filter (default) |
| billable | boolean | – | Filter by billable status (true = billable only, false = non-billable only) |
| dateWorkedAfter | string | – | Filter entries worked on or after this date (ISO format, e.g. 2026-01-01) |
| dateWorkedBefore | string | – | Filter entries worked on or before this date (ISO format) |
| page | number | – | – |
| pageSize | number | – | Max 500 |
| projectId | number | – | Filter by project ID |
| resourceId | number | – | Filter by resource (user) ID |
| taskId | number | – | Filter by task ID |
| ticketId | number | – | Filter by ticket ID |
No output schema declared.
No examples provided.
autotask_test_connection ~17
Test Autotask API connection
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
autotask_update_company ~547
Update company record. invoiceTemplateID sets payment terms (103=Due on Receipt, 104=NET 30). Billing address fields separate from regular address.
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | – | Regular address (distinct from billingAddress1) |
| address2 | string | – | – |
| billToAddressToUse | number | – | 1 = use bill-to fields explicitly |
| billToAttention | string | – | Bill-to attention name |
| billToCity | string | – | Bill-to city |
| billToCompanyLocationID | number | – | Bill-to company location ID |
| billToCountryID | number | – | Bill-to country ID |
| billToState | string | – | Bill-to state/province |
| billToZipCode | string | – | Bill-to ZIP/postal code |
| billingAddress1 | string | – | For invoices (separate from address1) |
| billingAddress2 | string | – | Billing address line 2 |
| city | string | – | – |
| classification | number | – | Company classification picklist ID |
| companyName | string | – | – |
| companyType | number | – | Company type picklist ID (e.g. Customer, Prospect, Vendor) |
| countryID | number | – | e.g. 237 for United States |
| id | number | yes | – |
| invoiceEmailMessageID | number | – | Default email-message template ID used when invoicing this company |
| invoiceMethod | number | – | Invoice delivery method picklist ID (e.g. 2=Email) |
| invoiceTemplateID | number | – | Invoice template ID applied to this company. Acts as the payment-terms selector (e.g. 103=Due on Receipt, 104=NET 30). |
| isActive | boolean | – | – |
| isTaxExempt | boolean | – | Whether the company is tax-exempt. Note: Autotask field name is `isTaxExempt` — not `taxExempt`. |
| ownerResourceID | number | – | Resource ID of the account owner |
| phone | string | – | – |
| postalCode | string | – | – |
| purchaseOrderTemplateID | number | – | Default purchase-order template ID for this company |
| quoteEmailMessageID | number | – | Default email-message template ID used when sending quotes |
| quoteTemplateID | number | – | Default quote template ID for this company |
| state | string | – | – |
| taxID | string | – | Tax registration / FEIN / VAT identifier string |
| taxRegionID | number | – | Tax region ID (capital ID suffix per Autotask convention) |
| webAddress | string | – | Website URL (field name is webAddress) |
No output schema declared.
No examples provided.
autotask_update_company_site_configuration ~72
Update company site configuration. Fields are tenant-defined; call get first.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | The company site configuration record ID to update (obtained from autotask_get_company_site_configuration). |
| updates | object | yes | Object containing the site configuration fields to update. Field names are tenant-specific. |
No output schema declared.
No examples provided.
autotask_update_contact ~242
Update contact record. Only provided fields are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| addressLine | string | – | Address line (primary) |
| addressLine1 | string | – | Address line 1 (secondary) |
| city | string | – | City |
| countryID | number | – | Country ID (Autotask Countries entity) |
| emailAddress | string | – | Primary email address |
| firstName | string | – | – |
| id | number | yes | Contact ID to update |
| isActive | boolean | – | Whether the contact is active |
| lastName | string | – | – |
| mobilePhone | string | – | Mobile phone number |
| phone | string | – | Primary phone number |
| primaryContact | boolean | – | Whether this contact is the primary contact for their company |
| state | string | – | State/province |
| title | string | – | Job title |
| userDefinedFields | array | – | User-defined (custom) fields for the contact, as an array of { name, value } objects matching the Autotask REST API shape. Contacts support UDFs (hasUserDefinedFields: true). |
| zipCode | string | – | Postal/ZIP code |
No output schema declared.
No examples provided.
autotask_update_contract ~485
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.
| Name | Type | Req | Description |
|---|---|---|---|
| billToCompanyContactID | number | – | Bill-to contact ID |
| billToCompanyID | number | – | Bill-to company ID |
| billingPreference | number | – | Billing preference picklist ID |
| companyID | number | – | Company ID |
| contactID | number | – | Primary contact ID |
| contractCategory | number | – | Contract category picklist ID |
| contractExclusionSetID | number | – | Contract exclusion set ID |
| contractName | string | – | Contract name |
| contractNumber | string | – | External-facing contract number |
| contractPeriodType | number | – | Period type picklist ID |
| contractType | number | – | Contract type picklist ID |
| description | string | – | Contract description / notes |
| endDate | string | – | Contract end date (ISO YYYY-MM-DD) |
| estimatedCost | number | – | Estimated cost |
| estimatedHours | number | – | Estimated hours |
| estimatedRevenue | number | – | Estimated revenue |
| exclusionContractID | number | – | Exclusion contract ID |
| id | number | yes | Contract ID to update |
| internalCurrencyOverageBillingRate | number | – | Overage rate in internal currency |
| internalCurrencySetupFee | number | – | Setup fee in internal currency |
| isDefaultContract | boolean | – | Whether this is the default contract for the company |
| opportunityID | number | – | Originating opportunity ID |
| organizationalLevelAssociationID | number | – | Org level association ID |
| overageBillingRate | number | – | Overage billing rate |
| purchaseOrderNumber | string | – | Customer purchase order number |
| renewedContractID | number | – | ID of the contract this renewed |
| serviceLevelAgreementID | number | – | SLA ID |
| setupFee | number | – | Setup fee amount |
| setupFeeBillingCodeID | number | – | Billing code ID for the setup fee |
| startDate | string | – | Contract start date (ISO YYYY-MM-DD) |
| status | number | – | Contract status (1=In Effect, 0=Inactive) |
| timeReportingRequiresStartAndStopTimes | number | – | Whether time entries require start/stop times |
No output schema declared.
No examples provided.
autotask_update_contract_service ~146
Update an existing ContractService line on a Contract. Pass only fields you want to change.
| Name | Type | Req | Description |
|---|---|---|---|
| adjustedPrice | number | – | Adjusted price |
| contractID | number | yes | Parent Contract ID |
| id | number | yes | ContractService record ID to update |
| internalCurrencyUnitPrice | number | – | Unit price in internal currency |
| invoiceDescription | string | – | Override invoice description for this line |
| quoteItemID | number | – | Originating quote item ID |
| serviceID | number | – | Service catalog ID |
| unitCost | number | – | Unit cost for the service line |
| unitPrice | number | – | Unit price for the service line |
No output schema declared.
No examples provided.
autotask_update_project ~278
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.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedResourceID | number | – | Primary assigned resource (project manager) ID. Note: Autotask may also require assignedResourceRoleID to be set alongside this field. |
| assignedResourceRoleID | number | – | Role ID for the assigned resource. Required by Autotask when assignedResourceID is provided. |
| departmentID | number | – | Department ID owning the project |
| description | string | – | Project description |
| endDateTime | string | – | Project end date/time (ISO 8601) |
| estimatedTime | number | – | Estimated time for the project, in hours |
| projectId | number | yes | The ID of the project to update |
| projectLeadResourceID | number | – | Project lead resource ID |
| projectName | string | – | Project name |
| startDateTime | string | – | Project start date/time (ISO 8601) |
| status | number | – | Project status (1=New, 2=In Progress, 5=Complete). Set to 5 to mark the project complete. |
| userDefinedFields | array | – | User-defined field values to set on the project (Autotask REST-native shape) |
No output schema declared.
No examples provided.
autotask_update_quote_item ~115
Update an existing quote item (quantity, price, etc.)
| Name | Type | Req | Description |
|---|---|---|---|
| isOptional | boolean | – | Updated optional status |
| lineDiscount | number | – | Updated line discount |
| percentageDiscount | number | – | Updated percentage discount |
| quantity | number | – | Updated quantity |
| quoteItemId | number | yes | The quote item ID to update |
| sortOrderID | number | – | Updated sort order |
| unitDiscount | number | – | Updated per-unit discount |
| unitPrice | number | – | Updated unit price |
No output schema declared.
No examples provided.
autotask_update_service_call ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| complete | boolean | – | Set to true to mark the service call as complete/closed |
| description | string | – | Updated description |
| endDateTime | string | – | Updated end date/time (ISO 8601 format) |
| serviceCallId | number | yes | The service call ID to update |
| startDateTime | string | – | Updated start date/time (ISO 8601 format) |
| status | number | – | Updated status picklist ID |
No output schema declared.
No examples provided.
autotask_update_ticket ~293
Update ticket record. Only provided fields are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedResourceID | number | – | Assigned resource ID. If set, assignedResourceRoleID is also required by Autotask. |
| assignedResourceRoleID | number | – | Role ID for the assigned resource. Required by Autotask when assignedResourceID is set. |
| contactID | number | – | Contact ID for the ticket |
| description | string | – | – |
| dueDateTime | string | – | Due date and time in ISO 8601 format (e.g. 2026-03-15T17:00:00Z) |
| issueType | number | – | First-level issue type ID (picklist). Required context for subIssueType. Use autotask_get_field_info (entityType "Tickets", fieldName "issueType") to discover valid values. |
| priority | number | – | Ticket priority ID (use autotask_list_ticket_priorities to find valid IDs) |
| status | number | – | Ticket status ID (use autotask_list_ticket_statuses to find valid IDs) |
| subIssueType | number | – | Sub issue type ID (picklist). Must be valid for the selected issueType. Use autotask_get_field_info (entityType "Tickets", fieldName "subIssueType") to discover valid values. |
| ticketId | number | yes | The ID of the ticket to update |
| title | string | – | – |
No output schema declared.
No examples provided.
autotask_update_ticket_charge ~111
Update an existing ticket charge. Only fields provided will be changed.
| Name | Type | Req | Description |
|---|---|---|---|
| billableToAccount | boolean | – | Updated billable status |
| chargeId | number | yes | The charge ID to update |
| description | string | – | Updated description |
| name | string | – | Updated charge name |
| status | number | – | Updated status |
| unitCost | number | – | Updated unit cost |
| unitPrice | number | – | Updated unit price |
| unitQuantity | number | – | Updated quantity |
No output schema declared.
No examples provided.
How do I install the Autotask MCP server?
Autotask runs locally as a container image, launched with docker run --rm -i -e AUTOTASK_USERNAME -e AUTOTASK_SECRET -e AUTOTASK_INTEGRATION_CODE -e AUTOTASK_API_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/autotask-mcp:v2.32.10. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/wyre-technology/autotask-mcp:v2.32.10
claude mcp add wyre-technology-autotask-mcp -- docker run --rm -i -e AUTOTASK_USERNAME -e AUTOTASK_SECRET -e AUTOTASK_INTEGRATION_CODE -e AUTOTASK_API_URL -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/autotask-mcp:v2.32.10
This image reads AUTOTASK_USERNAME, AUTOTASK_SECRET, AUTOTASK_INTEGRATION_CODE, AUTOTASK_API_URL, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Autotask MCP server?
Autotask is an MCP server listed in the public MCP registry as io.github.wyre-technology/autotask-mcp. MCP server for Kaseya Autotask PSA, companies, tickets, projects, time entries, and more. This page covers its container image (ghcr.io/wyre-technology/autotask-mcp:v2.32.10).
Is the Autotask MCP server safe to use?
Autotask scores 49 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Autotask MCP server expose?
Autotask exposes 101 tools: autotask_test_connection, autotask_search_companies, autotask_create_company, autotask_update_company, autotask_get_company_site_configuration, and 96 more. Their descriptions and schemas cost roughly 12,437 tokens of context every time the server is loaded.
Is the Autotask MCP server still maintained?
Autotask is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Autotask MCP server under?
Autotask declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.