Autotask
OCI · GHCR.IO/WYRE-AI/AUTOTASK-MCP
MCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.
Available components
Last scanned (12 hours ago)
Scores higher than 71% of OCI servers
Category Project Management
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 & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 15370 tokens (~130/item across 118 items; 110 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 Management57
- Stability observed for 17 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
- 92% 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 112 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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +38
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.47 ▲ functional
- Package version: v2.39.0 → v2.39.7 functional
- 14 Oct 26 0
- Package version: v2.39.5 → v2.39.7 functional
- Package version: v2.39.5 → v2.39.6 functional
- 13 Oct 26 0
- Package version: v2.39.0 → v2.39.5 functional
- 12 Oct 26 0
- Package version: v2.39.4 → v2.39.5 functional
- 10 Oct 26 0
- Package version: v2.39.2 → v2.39.4 functional
- 7 Oct 26 −32
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: v2.39.0 → v2.39.2 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 18 Oct 2026 · Analysed oci/ghcr.io/wyre-ai/autotask-mcp@v2.39.7
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_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_opportunity ~690
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Total revenue. Setting this replaces the revenue breakdown: onetimeRevenue becomes this value and recurring revenue is cleared. To keep recurring revenue, set the per-period fields instead. |
| contactID | number | – | Contact ID. Must be an active contact at the opportunity's company. |
| cost | number | – | Total cost. Setting this replaces the cost breakdown: onetimeCost becomes this value and recurring cost is cleared. To keep recurring cost, set the per-period fields instead. |
| description | string | – | Opportunity description |
| lossReason | number | – | Loss reason picklist value ID, for a lost opportunity (use autotask_get_field_info to find valid values) |
| lossReasonDetail | string | – | Loss reason detail (max 500 characters) |
| monthlyCost | number | – | Monthly cost |
| monthlyRevenue | number | – | Monthly revenue |
| nextStep | string | – | Next step (max 500 characters) |
| onetimeCost | number | – | One-time cost |
| onetimeRevenue | number | – | One-time revenue |
| opportunityCategoryID | number | – | Opportunity category picklist value ID |
| opportunityId | number | yes | The ID of the opportunity to update |
| ownerResourceID | number | – | Owner resource ID (the sales rep or account manager) |
| probability | number | – | Win probability percentage (0-100) |
| projectedCloseDate | string | – | Projected close date (YYYY-MM-DD). Must not be before the start date. |
| quarterlyCost | number | – | Quarterly cost |
| quarterlyRevenue | number | – | Quarterly revenue |
| semiannualCost | number | – | Semi-annual cost |
| semiannualRevenue | number | – | Semi-annual revenue |
| stage | number | – | Stage picklist value ID (use autotask_get_field_info to find valid values) |
| status | number | – | Status: 0=Not Ready To Buy, 1=Active, 2=Lost, 3=Closed, 4=Implemented |
| title | string | – | Opportunity name/title |
| totalAmountMonths | number | – | Number of months the recurring revenue/cost is totalled over (e.g., 12 for annual) |
| useQuoteTotals | boolean | – | Take revenue and cost from the primary quote. Setting true overwrites every revenue and cost field; with no quote attached, they all become 0. |
| userDefinedFields | array | – | User-defined field values to set on the opportunity (Autotask REST-native shape) |
| winReason | number | – | Win reason picklist value ID, for a won opportunity (use autotask_get_field_info to find valid values) |
| winReasonDetail | string | – | Win reason detail (max 500 characters) |
| yearlyCost | number | – | Yearly cost |
| yearlyRevenue | number | – | Yearly revenue |
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 ~367
Update ticket record. Only provided fields are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedResourceID | number | – | Assigned resource ID. Autotask also requires that resource's role: pass assignedResourceRoleID or assignedResourceRoleName, or omit both and the resource's only active role is used (several roles = a… |
| assignedResourceRoleID | number | – | Role ID for the assigned resource — one of that resource's roles (see autotask_search_resource_roles). Resolved automatically when omitted. |
| assignedResourceRoleName | string | – | Name of the assigned resource's role, e.g. "Help Desk", used instead of assignedResourceRoleID when the resource holds several roles. |
| 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.
autotask_update_ticket_checklist_item ~105
Update a checklist item on a ticket — edit text, mark complete/incomplete, or change position.
| Name | Type | Req | Description |
|---|---|---|---|
| isCompleted | boolean | – | Mark the item complete (true) or incomplete (false) |
| itemId | number | yes | The checklist item ID to update |
| itemName | string | – | New text for the checklist item |
| position | number | – | New ordering position for the item |
| ticketId | number | yes | The parent ticket ID |
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-ai/autotask-mcp:v2.39.7. 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-ai/autotask-mcp
claude mcp add wyre-ai-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-ai/autotask-mcp:v2.39.7
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-AI/autotask-mcp. MCP server for Kaseya Autotask PSA, companies, tickets, projects, time entries, and more. This page covers its container image (ghcr.io/wyre-ai/autotask-mcp).
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 110 tools: autotask_test_connection, autotask_search_companies, autotask_create_company, autotask_update_company, autotask_get_company_site_configuration, and 105 more. Their descriptions and schemas cost roughly 14,716 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 18 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.