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 (11 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_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.
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_get_ticket_note_attachment ~324
Get an uploaded file attachment on a ticket note (distinct from attachments on the ticket itself). With includeData=false (default) returns metadata only — any file bytes Autotask included are omitted. With includeData=true returns the base64 file bytes from GET /TicketNotes/{ticketNoteId}/Attachments/{attachmentId}, which is parent-scoped and is the call that populates data for note attachments. If that response omits data, falls back to GET /TicketNoteAttachments/{id} and uses those bytes only when ticketNoteID or parentID matches the note; if the bytes cannot be verified, returns an error instead of reporting the attachment as missing. 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 from the note-scoped attachment. Default false returns metadata only (bytes are omitted even if Autotask sent them). |
| 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. |
| ticketNoteId | number | yes | The ticket note ID the attachment belongs to (from autotask_search_ticket_notes) |
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 ~240
Escape hatch for Autotask REST endpoints not yet wrapped by a typed tool. Prefer typed tools. The path is relative to the zone v1.0 base (https://webservices<N>.autotask.net/ATServicesRest/v1.0) and must not start with /v1.0. Searches are POST /{Entity}/query with a body of {"filter":[...]}. Example: POST /Companies/query {"filter":[{"op":"eq","field":"id","value":175}]}. Auth headers are added automatically. queryParams is a flat object of string/number/boolean values appended to the path.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | Optional JSON body. Searches use {"filter":[{"op":"eq","field":"id","value":0}]} |
| method | string | yes | HTTP method |
| path | string | yes | Relative path under the v1.0 base. Must not start with /v1.0 (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_contract_service_bundle_units ~87
Billed unit rows for bundle lines on a contract (ContractServiceBundleUnits), active on a given day (default today). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| activeOn | string | – | ISO date (YYYY-MM-DD). Default: today. |
| contractID | number | yes | Contract ID |
| pageSize | number | – | Max rows (default 200, max 500) |
No output schema declared.
No examples provided.
autotask_search_contract_service_bundles ~60
List the service-bundle line items on a contract (ContractServiceBundles). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| contractID | number | yes | Contract ID |
| pageSize | number | – | Max rows (default 100, max 500) |
No output schema declared.
No examples provided.
autotask_search_contract_service_units ~115
Billed unit rows for a contract (ContractServiceUnits): the quantity and contract price of each service line over a date range. By default returns only rows active today, i.e. what is currently being invoiced. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| activeOn | string | – | ISO date (YYYY-MM-DD). Return rows whose start/end range covers this day. Default: today. |
| contractID | number | yes | Contract ID |
| pageSize | number | – | Max rows (default 200, max 500) |
No output schema declared.
No examples provided.
autotask_search_contract_services ~96
List the service line items on a contract (ContractServices): which catalog services are on the contract and at what contract-specific unit price. Read-only. Pair with autotask_search_contract_service_units for billed quantities, or use autotask_get_contract_recurring_lines for both in one call.
| Name | Type | Req | Description |
|---|---|---|---|
| contractID | number | yes | Contract ID |
| pageSize | number | – | Max rows (default 100, max 500) |
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_resource_roles ~137
List the billing roles a resource (user) holds in Autotask, with names and role IDs. A ticket assigned to a resource and every ticket/task time entry need one of these role IDs; this is where to find them instead of guessing. Give resourceId or resourceName. Active roles only unless includeInactive is true.
| Name | Type | Req | Description |
|---|---|---|---|
| includeInactive | boolean | – | Also list inactive role assignments (default false) |
| resourceId | number | – | Resource (user) ID |
| resourceName | string | – | Resource name, e.g. "Ryan Rampersaud", resolved to a resourceId when resourceId is not given |
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_note_attachments ~127
Search for attachments on a specific ticket note — use this when autotask_search_ticket_notes returns a note with an empty or unhelpful `description`, since the real content is often a pasted image or file living on the note rather than in its text. Each note triggers a separate query — scope the parent note list before iterating.
| Name | Type | Req | Description |
|---|---|---|---|
| pageSize | number | – | Number of results to return (default: 10, max: 50) |
| ticketNoteId | number | yes | The ticket note ID to search attachments for (from autotask_search_ticket_notes) |
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 ~300
Search for time entries in Autotask. Returns 25 results per page by default. Time entries can be filtered by resource, ticket, task, date range, or approval status. Use approvalStatus="unapproved" to find entries not yet posted. There is no project filter — Autotask time entries have no project field; to get a project's time, call autotask_search_tasks with that projectID and filter by the returned taskId values. Common fan-out target — scope by date range first to avoid Autotask's API threshold.
| 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 |
| 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.
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.