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 (22 hours ago)
Scores higher than 74% 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_create_company ~85
Create new company record
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | – | – |
| city | string | – | – |
| companyName | string | yes | – |
| companyType | number | yes | – |
| isActive | boolean | – | – |
| ownerResourceID | number | – | – |
| phone | string | – | – |
| postalCode | string | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
autotask_create_company_note ~66
Create a new note for a company
| Name | Type | Req | Description |
|---|---|---|---|
| actionType | number | – | Action type for the note |
| companyId | number | yes | The company ID to add the note to |
| description | string | yes | Note content |
| title | string | – | Note title |
No output schema declared.
No examples provided.
autotask_create_contact ~66
Create new contact record
| Name | Type | Req | Description |
|---|---|---|---|
| companyID | number | yes | Company ID for the contact |
| emailAddress | string | – | – |
| firstName | string | yes | – |
| lastName | string | yes | – |
| phone | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
autotask_create_contract ~486
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).
| Name | Type | Req | Description |
|---|---|---|---|
| billToCompanyContactID | number | – | Bill-to contact ID |
| billToCompanyID | number | – | Bill-to company ID |
| billingPreference | number | – | Billing preference picklist ID |
| companyID | number | yes | Company ID the contract is associated with |
| contactID | number | – | Primary contact ID for the contract |
| contractCategory | number | yes | Contract category picklist ID |
| contractExclusionSetID | number | – | Contract exclusion set ID |
| contractName | string | yes | Contract name |
| contractNumber | string | – | External-facing contract number |
| contractPeriodType | number | – | Period type picklist ID |
| contractType | number | yes | Contract type picklist ID |
| description | string | – | Contract description / notes |
| endDate | string | yes | Contract end date (ISO YYYY-MM-DD) |
| estimatedCost | number | – | Estimated cost |
| estimatedHours | number | – | Estimated hours |
| estimatedRevenue | number | – | Estimated revenue |
| exclusionContractID | number | – | Exclusion contract ID |
| 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 | yes | 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_create_contract_service ~137
Add a ContractService (service line item) to an existing Contract.
| Name | Type | Req | Description |
|---|---|---|---|
| adjustedPrice | number | – | Adjusted price |
| contractID | number | yes | Parent Contract ID |
| internalCurrencyUnitPrice | number | – | Unit price in internal currency |
| invoiceDescription | string | – | Override invoice description for this line |
| quoteItemID | number | – | Originating quote item ID, if any |
| serviceID | number | yes | Service catalog ID being attached to the contract |
| unitCost | number | – | Unit cost for the service line |
| unitPrice | number | yes | Unit price for the service line |
No output schema declared.
No examples provided.
autotask_create_contracts_bulk ~92
Create multiple contract shells (header records, no service lines) in one call — e.g. onboarding a customer with several location-based contracts. Shells are created one at a time; a failure on one shell does not stop the rest, and each item reports its own success or error.
| Name | Type | Req | Description |
|---|---|---|---|
| contracts | array | yes | Contract shells to create, in order. Same fields as autotask_create_contract. |
No output schema declared.
No examples provided.
autotask_create_expense_item ~163
Create an expense item on an existing expense report
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Expense amount |
| companyId | number | – | Associated company ID (0 for internal) |
| description | string | yes | Line item description |
| expenseCategory | number | yes | Expense category picklist ID |
| expenseDate | string | yes | Date of expense (YYYY-MM-DD format) |
| expenseReportId | number | yes | The expense report ID to add the item to |
| haveReceipt | boolean | – | Whether a receipt is attached |
| isBillableToCompany | boolean | – | Whether billable to company |
| isReimbursable | boolean | – | Whether this expense is reimbursable |
| paymentType | number | – | Payment type picklist ID |
No output schema declared.
No examples provided.
autotask_create_expense_report ~71
Create a new expense report
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Expense report description |
| name | string | yes | Expense report name |
| submitterId | number | yes | The resource ID of the submitter |
| weekEndingDate | string | yes | Week ending date (YYYY-MM-DD format) |
No output schema declared.
No examples provided.
autotask_create_opportunity ~291
Create a new sales opportunity in Autotask
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Revenue amount (default: 0, set useQuoteTotals=true to calculate from quotes) |
| companyId | number | yes | Company ID for the opportunity |
| contactId | number | – | Contact ID for the opportunity |
| cost | number | – | Cost amount (default: 0) |
| description | string | – | Opportunity description |
| opportunityCategoryID | number | – | Opportunity category picklist value ID |
| ownerResourceId | number | yes | Owner resource ID (the sales rep or account manager) |
| probability | number | – | Win probability percentage (0-100, default: 50) |
| projectedCloseDate | string | yes | Projected close date (YYYY-MM-DD) |
| stage | number | yes | Stage picklist value ID (use autotask_get_field_info to find valid values) |
| startDate | string | yes | Start date (YYYY-MM-DD) |
| status | number | yes | Status: 0=Not Ready To Buy, 1=Active, 2=Lost, 3=Closed, 4=Implemented |
| title | string | yes | Opportunity name/title |
| totalAmountMonths | number | – | Number of months to calculate totals for (e.g., 12 for annual) |
| useQuoteTotals | boolean | – | Whether to calculate totals from linked quotes (default: true) |
No output schema declared.
No examples provided.
autotask_create_phase ~93
Create a new phase in an Autotask project
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Phase description |
| dueDate | string | – | Phase due date (ISO format) |
| estimatedHours | number | – | Estimated hours for the phase |
| projectID | number | yes | Project ID for the phase |
| startDate | string | – | Phase start date (ISO format) |
| title | string | yes | Phase title |
No output schema declared.
No examples provided.
autotask_create_project ~168
Create a new project in Autotask
| Name | Type | Req | Description |
|---|---|---|---|
| companyID | number | yes | Company ID for the project |
| description | string | – | Project description |
| endDate | string | – | Project end date (YYYY-MM-DD) |
| estimatedHours | number | – | Estimated hours for the project |
| projectLeadResourceID | number | – | Project manager resource ID |
| projectName | string | yes | Project name |
| projectType | number | yes | Project type (2=Proposal, 3=Template, 4=Internal, 5=Client, 8=Baseline). Required. |
| startDate | string | – | Project start date (YYYY-MM-DD) |
| status | number | yes | Project status (1=New, 2=In Progress, 5=Complete) |
No output schema declared.
No examples provided.
autotask_create_project_note ~145
Create a new note for a project
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Note content |
| isAnnouncement | boolean | – | Whether this note is an announcement. Defaults to false. |
| noteType | number | – | Note type (1=General, 2=Appointment, 3=Task, 4=Ticket, 5=Project, 6=Opportunity) |
| projectId | number | yes | The project ID to add the note to |
| publish | number | – | Publish visibility (1=All Autotask Users, 2=Internal Project Team, 3=Project Team). Defaults to 1. |
| title | string | – | Note title |
No output schema declared.
No examples provided.
autotask_create_quote ~101
Create a new quote
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | number | yes | Company ID for the quote |
| contactId | number | – | Contact ID for the quote |
| description | string | – | Quote description |
| effectiveDate | string | – | Effective date (YYYY-MM-DD format) |
| expirationDate | string | – | Expiration date (YYYY-MM-DD format) |
| name | string | – | Quote name |
| opportunityId | number | – | Associated opportunity ID |
No output schema declared.
No examples provided.
autotask_create_quote_item ~345
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Item description |
| isOptional | boolean | – | Whether this is an optional line item (default: false) |
| lineDiscount | number | – | Line-level discount amount (default: 0) |
| name | string | – | Item name (auto-populated for service/product types) |
| percentageDiscount | number | – | Percentage discount (default: 0) |
| productID | number | – | Product ID to link (mutually exclusive with serviceID/serviceBundleID) |
| quantity | number | yes | Quantity of the item |
| quoteId | number | yes | The quote ID to add this item to |
| quoteItemType | number | – | Quote item type (auto-determined if omitted): 1=Product, 2=Cost, 3=Labor, 4=Expense, 6=Shipping, 11=Service, 12=ServiceBundle |
| serviceBundleID | number | – | Service Bundle ID to link (mutually exclusive with serviceID/productID) |
| serviceID | number | – | Service ID to link (mutually exclusive with productID/serviceBundleID) |
| sortOrderID | number | – | Sort order for display |
| unitCost | number | – | Unit cost for the item |
| unitDiscount | number | – | Per-unit discount amount (default: 0) |
| unitPrice | number | – | Unit price for the item |
No output schema declared.
No examples provided.
autotask_create_service_call ~176
Create a new service call in Autotask. Service calls are used to schedule and plan work on tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| companyID | number | – | Company ID this service call is for |
| companyLocationID | number | – | Company location ID (optional) |
| complete | boolean | – | Whether this service call is complete (default: false) |
| description | string | yes | Description of the service call |
| endDateTime | string | yes | Scheduled end date/time (ISO 8601 format) |
| startDateTime | string | yes | Scheduled start date/time (ISO 8601 format, e.g. 2026-03-22T09:00:00Z) |
| status | number | – | Status picklist ID (use autotask_get_field_info with entityType "ServiceCalls" to find valid values) |
No output schema declared.
No examples provided.
autotask_create_service_call_ticket ~67
Link a ticket to a service call. This associates the ticket with the service call for scheduling purposes.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceCallID | number | yes | The service call ID to link the ticket to |
| ticketID | number | yes | The ticket ID to link to the service call |
No output schema declared.
No examples provided.
autotask_create_service_call_ticket_resource ~83
Assign a resource (technician) to a service call ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| resourceID | number | yes | The resource (technician) ID to assign |
| roleID | number | – | The role ID for the resource on this service call (optional) |
| serviceCallTicketID | number | yes | The service call ticket ID to assign the resource to |
No output schema declared.
No examples provided.
autotask_create_task ~157
Create a new task in Autotask
| Name | Type | Req | Description |
|---|---|---|---|
| assignedResourceID | number | – | Assigned resource ID |
| description | string | – | Task description |
| endDateTime | string | – | Task end date/time (ISO format) |
| estimatedHours | number | – | Estimated hours for the task |
| projectID | number | yes | Project ID for the task |
| startDateTime | string | – | Task start date/time (ISO format) |
| status | number | yes | Task status (1=New, 2=In Progress, 5=Complete) |
| taskType | number | – | Task type (1=FixedWork, 2=FixedDuration). Defaults to 1. |
| title | string | yes | Task title |
No output schema declared.
No examples provided.
autotask_create_ticket ~521
Create new ticket record
| 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. |
| billingCodeID | number | – | Work type / billing code ID used for billing this ticket. |
| companyID | number | yes | Company ID for the ticket |
| contactID | number | – | Contact ID for the ticket |
| description | string | yes | – |
| estimatedHours | number | – | Estimated hours of work for the ticket. |
| 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 | – | – |
| projectID | number | – | Project ID to associate the ticket with. Links the ticket to an existing project. |
| queueID | number | – | Queue ID to route the ticket to. Use autotask_list_queues to discover valid IDs. |
| resolution | string | – | Ticket-level resolution text. This is the Resolution field on the ticket itself, NOT a ticket note. |
| serviceLevelAgreementID | number | – | Service Level Agreement (SLA) ID to apply to the ticket. |
| source | number | – | Ticket source ID (picklist, e.g. Phone, Email, Portal). Use autotask_get_field_info (entityType "Tickets", fieldName "source") to discover valid values. |
| status | number | – | – |
| 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. |
| ticketAdditionalContacts | array | – | Additional contact IDs to associate with the ticket (beyond the primary contactID). |
| ticketCategory | number | – | Ticket category ID (picklist). Use autotask_get_field_info with entityType "Tickets" and fieldName "ticketCategory" to discover valid values. |
| ticketType | number | – | Ticket type ID (picklist, e.g. Service Request, Incident, Problem, Change). |
| title | string | yes | – |
| userDefinedFields | array | – | User-defined (custom) fields for the ticket, as an array of { name, value } objects matching the Autotask REST API shape. |
No output schema declared.
No examples provided.
autotask_create_ticket_attachment ~283
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..." }
| Name | Type | Req | Description |
|---|---|---|---|
| contentType | string | – | MIME type of the file (e.g. "image/png", "application/pdf"). Optional. |
| data | string | yes | Base64-encoded file content. Maximum decoded size: 3 MB (Autotask ticket attachment limit). Example: read a file and pass its base64 representation here. |
| fullPath | string | – | Original filename including any path. Defaults to `title` if not provided. |
| publish | number | – | Visibility: 1 = All Autotask Users (default), 2 = Internal Users Only |
| ticketId | number | yes | The ticket ID to attach the file to |
| title | string | yes | Display title for the attachment (typically the filename, e.g. "screenshot.png") |
No output schema declared.
No examples provided.
autotask_create_ticket_charge ~202
Create charge on ticket for materials, costs, or expenses.
| Name | Type | Req | Description |
|---|---|---|---|
| billableToAccount | boolean | – | Whether this charge is billable to the client (default: true) |
| billingCodeID | number | – | Billing code ID for categorization |
| chargeType | number | yes | Charge type picklist ID (use autotask_get_field_info with entityType "TicketCharges" to find valid values) |
| datePurchased | string | – | Date the charge was incurred (YYYY-MM-DD format) |
| description | string | – | Charge description |
| name | string | yes | Charge name/title |
| productID | number | – | Associated product ID (optional) |
| status | number | – | Charge status picklist ID |
| ticketID | number | yes | Ticket ID to add the charge to |
| unitCost | number | – | Cost per unit |
| unitPrice | number | – | Price per unit |
| unitQuantity | number | – | Quantity of units |
No output schema declared.
No examples provided.
autotask_create_ticket_checklist_item ~84
Add a new checklist item to a ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| isCompleted | boolean | – | Whether the item starts in the completed state (default: false) |
| itemName | string | yes | The checklist item text |
| position | number | – | Optional ordering position for the item |
| ticketId | number | yes | The ticket ID to add the checklist item to |
No output schema declared.
No examples provided.
autotask_create_ticket_note ~188
Create a new note for a ticket
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Note content |
| noteType | number | yes | Note type picklist ID. Tenant-specific — call autotask_get_field_info with entityType "TicketNotes" and fieldName "noteType" to discover the exact label-to-ID mapping before calling this tool. Do not… |
| publish | number | yes | Publish/visibility picklist ID. Tenant-specific and security-sensitive (controls whether the note is visible to clients). Call autotask_get_field_info with entityType "TicketNotes" and fieldName "pub… |
| ticketId | number | yes | The ticket ID to add the note to |
| title | string | – | Note title |
No output schema declared.
No examples provided.
autotask_create_time_entry ~343
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category name for Regular Time entries (e.g., "Internal Meeting", "Office Management", "Training", "Research", "HR/Recruiting", "Travel Time", "Holiday", "PTO"). Required for Regular Time entries (wh… |
| dateWorked | string | yes | Date worked (YYYY-MM-DD format) |
| endDateTime | string | – | End date/time (ISO format) |
| hoursWorked | number | yes | Number of hours worked |
| internalNotes | string | – | Internal notes for the time entry |
| projectID | number | – | Project ID for the time entry (omit for Regular Time) |
| resourceID | number | – | Resource ID (user) logging the time. Can be omitted if resourceName is provided. |
| resourceName | string | – | Name of the resource/user (e.g., "Will Spence"). Will be resolved to a resourceID automatically. Use this instead of resourceID for convenience. |
| startDateTime | string | – | Start date/time (ISO format) |
| summaryNotes | string | yes | Summary notes for the time entry |
| taskID | number | – | Task ID for the time entry (for project work, omit for Regular Time) |
| ticketID | number | – | Ticket ID for the time entry (omit for Regular Time) |
No output schema declared.
No examples provided.
autotask_delete_quote_item ~76
⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a quote item (line item) from a quote. This action cannot be undone. Confirm with the user before invoking.
| Name | Type | Req | Description |
|---|---|---|---|
| quoteId | number | yes | The parent quote ID |
| quoteItemId | number | yes | The quote item ID to delete |
No output schema declared.
No examples provided.
autotask_delete_service_call ~61
⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a service call and all associated data. This action cannot be undone. Confirm with the user before invoking.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceCallId | number | yes | The service call ID to delete |
No output schema declared.
No examples provided.
autotask_delete_service_call_ticket ~65
⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently removes a ticket association from a service call. This action cannot be undone. Confirm with the user before invoking.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceCallTicketId | number | yes | The service call ticket record ID to delete |
No output schema declared.
No examples provided.
autotask_delete_service_call_ticket_resource ~69
⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently removes a resource assignment from a service call ticket. This action cannot be undone. Confirm with the user before invoking.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceCallTicketResourceId | number | yes | The service call ticket resource record ID to delete |
No output schema declared.
No examples provided.
autotask_delete_ticket_charge ~73
⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a ticket charge record and all associated billing data. This action cannot be undone. Confirm with the user before invoking.
| Name | Type | Req | Description |
|---|---|---|---|
| chargeId | number | yes | The charge ID to delete |
| ticketId | number | yes | The parent ticket ID |
No output schema declared.
No examples provided.
autotask_delete_ticket_checklist_item ~73
⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a checklist item from a ticket. This action cannot be undone. Confirm with the user before invoking.
| Name | Type | Req | Description |
|---|---|---|---|
| itemId | number | yes | The checklist item ID to delete |
| ticketId | number | yes | The parent ticket ID |
No output schema declared.
No examples provided.
autotask_execute_tool ~67
Execute any Autotask tool by name. Use after discovering tools via autotask_list_category_tools.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | Arguments to pass to the tool |
| toolName | string | yes | The tool name to execute (e.g., "autotask_search_tickets") |
No output schema declared.
No examples provided.
autotask_get_billing_item ~38
Get detailed information for a specific billing item by ID
| Name | Type | Req | Description |
|---|---|---|---|
| billingItemId | number | yes | The billing item ID to retrieve |
No output schema declared.
No examples provided.
autotask_get_company_note ~47
Get a specific company note by company ID and note ID
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | number | yes | The company ID |
| noteId | number | yes | The note ID to retrieve |
No output schema declared.
No examples provided.
autotask_get_company_site_configuration ~43
Get company site configuration records. Call first to discover available fields.
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | number | yes | The company ID whose site configuration records should be returned |
No output schema declared.
No examples provided.
autotask_get_contract ~34
Get a single contract by ID (header fields only, no service lines)
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Contract ID |
No output schema declared.
No examples provided.
autotask_get_expense_report ~34
Get a specific expense report by ID
| Name | Type | Req | Description |
|---|---|---|---|
| reportId | number | yes | The expense report ID to retrieve |
No output schema declared.
No examples provided.
autotask_get_field_info ~119
Get field definitions for an Autotask entity type, including picklist values. Useful for discovering valid values for any picklist field.
| Name | Type | Req | Description |
|---|---|---|---|
| entityType | string | yes | The Autotask entity type (e.g., "Tickets", "Companies", "Contacts", "Projects", "ProjectTasks", "TicketNotes"). Note: project tasks use "ProjectTasks" (or "Tasks" which auto-maps). See Autotask REST… |
| fieldName | string | – | Optional: filter to a specific field name |
No output schema declared.
No examples provided.
autotask_get_invoice_details ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| invoiceId | number | yes | The invoice ID to fetch |
No output schema declared.
No examples provided.
autotask_get_opportunity ~31
Get a specific opportunity by ID
| Name | Type | Req | Description |
|---|---|---|---|
| opportunityId | number | yes | The opportunity ID to retrieve |
No output schema declared.
No examples provided.
autotask_get_product ~30
Get a specific product by ID
| Name | Type | Req | Description |
|---|---|---|---|
| productId | number | yes | The product ID to retrieve |
No output schema declared.
No examples provided.
autotask_get_project_note ~47
Get a specific project note by project ID and note ID
| Name | Type | Req | Description |
|---|---|---|---|
| noteId | number | yes | The note ID to retrieve |
| projectId | number | yes | The project ID |
No output schema declared.
No examples provided.
autotask_get_quote ~30
Get a specific quote by ID
| Name | Type | Req | Description |
|---|---|---|---|
| quoteId | number | yes | The quote ID to retrieve |
No output schema declared.
No examples provided.
autotask_get_quote_item ~34
Get a specific quote item by ID
| Name | Type | Req | Description |
|---|---|---|---|
| quoteItemId | number | yes | The quote item ID to retrieve |
No output schema declared.
No examples provided.
autotask_get_service ~30
Get a specific service by ID
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | number | yes | The service ID to retrieve |
No output schema declared.
No examples provided.
autotask_get_service_bundle ~34
Get a specific service bundle by ID
| Name | Type | Req | Description |
|---|---|---|---|
| serviceBundleId | number | yes | The service bundle ID to retrieve |
No output schema declared.
No examples provided.
autotask_get_service_call ~34
Get a specific service call by ID
| Name | Type | Req | Description |
|---|---|---|---|
| serviceCallId | number | yes | The service call ID to retrieve |
No output schema declared.
No examples provided.
autotask_get_ticket_attachment ~228
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).
| Name | Type | Req | Description |
|---|---|---|---|
| attachmentId | number | yes | The attachment ID to retrieve |
| includeData | boolean | – | Set true to fetch the base64-encoded file bytes. Default false returns metadata only. |
| maxInlineBase64Bytes | number | – | Cap on base64 string length before data is stripped (default 750_000, ~560 KB raw). Only relevant when includeData=true. Raise carefully — your MCP client may reject oversized tool results. |
| ticketId | number | yes | The ticket ID the attachment belongs to |
No output schema declared.
No examples provided.
autotask_get_ticket_charge ~33
Get a specific ticket charge by ID
| Name | Type | Req | Description |
|---|---|---|---|
| chargeId | number | yes | The ticket charge ID to retrieve |
No output schema declared.
No examples provided.
autotask_get_ticket_details ~58
Get full ticket details including notes, time entries, and custom fields.
| Name | Type | Req | Description |
|---|---|---|---|
| fullDetails | boolean | – | Whether to return full ticket details (default: false for optimized data) |
| ticketID | number | yes | Ticket ID to retrieve |
No output schema declared.
No examples provided.
autotask_get_ticket_history ~54
Get a single ticket history entry by ID. Each entry records one audited change to a ticket field (who, when, before/after).
| Name | Type | Req | Description |
|---|---|---|---|
| historyId | number | yes | The ticket history entry ID to retrieve |
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.