# io.github.WYRE-AI/autotask-mcp MCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more. - **Type:** MCP server - **Trust:** 60/100 (B), scored on the content rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 2.33.1 - **Author:** io.github.WYRE-AI - **License:** Unknown - **Source:** https://github.com/WYRE-AI/autotask-mcp ## Trust 60/100 (B), scored on the content rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: clean - Obfuscation scan: clean - Evidence age: 0 days ## Security scan - **Status:** clean - **Scanned:** 2026-09-05T18:15:26.082Z - **Version scanned:** HEAD - **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it. ## Tools 40 declared. Statically extracted from the shipped source — a floor on the surface, not a census. - `autotask_test_connection` — Test Autotask API connection - `autotask_search_companies` — Search companies by name or status. Max 200/page. - `autotask_create_company` — Create new company record - `autotask_update_company` — Update company record. invoiceTemplateID sets payment terms (103=Due on Receipt, 104=NET 30). Billing address fields separate from regular address. - `autotask_get_company_site_configuration` — Get company site configuration records. Call first to discover available fields. - `autotask_update_company_site_configuration` — Update company site configuration. Fields are tenant-defined; call get first. - `autotask_search_contacts` — Search contacts by name, email, or company. Max 200/page. - `autotask_create_contact` — Create new contact record - `autotask_update_contact` — Update contact record. Only provided fields are changed. - `autotask_search_tickets` — Search tickets by company, queue, status, priority. Use autotask_get_ticket_details for full data. Max 500/page. - `autotask_get_ticket_details` — Get full ticket details including notes, time entries, and custom fields. - `autotask_create_ticket` — Create new ticket record - `autotask_update_ticket` — Update ticket record. Only provided fields are changed. - `autotask_get_ticket_charge` — Get a specific ticket charge by ID - `autotask_search_ticket_charges` — Search ticket charges (materials, costs, expenses). Provide ticketId for best performance. Max 10 if unfiltered. - `autotask_create_ticket_charge` — Create charge on ticket for materials, costs, or expenses. - `autotask_update_ticket_charge` — Update an existing ticket charge. Only fields provided will be changed. - `autotask_delete_ticket_charge` — ⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a ticket charge - `autotask_get_ticket_history` — Get a single ticket history entry by ID. Each entry records one audited change to a ticket field (who, when, before/after). - `autotask_search_ticket_history` — 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 th - `autotask_create_time_entry` — 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 - `autotask_search_projects` — Search for projects in Autotask. Returns 25 results per page by default. Use page parameter for more results. - `autotask_create_project` — Create a new project in Autotask - `autotask_update_project` — 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. - `autotask_search_resources` — Search for resources (users) in Autotask. Returns 25 results per page by default. Use page parameter for more results. - `autotask_get_ticket_note` — Get a specific ticket note by ticket ID and note ID - `autotask_search_ticket_notes` — Search for notes on a specific ticket. Iterating across many tickets trips Autotask's per-integration API threshold — scope the parent list first. - `autotask_create_ticket_note` — Create a new note for a ticket - `autotask_search_ticket_checklist_items` — 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 I - `autotask_create_ticket_checklist_item` — Add a new checklist item to a ticket. - `autotask_update_ticket_checklist_item` — Update a checklist item on a ticket — edit text, mark complete/incomplete, or change position. - `autotask_delete_ticket_checklist_item` — ⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a checklist item - `autotask_get_project_note` — Get a specific project note by project ID and note ID - `autotask_search_project_notes` — 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, da - `autotask_create_project_note` — Create a new note for a project - `autotask_get_company_note` — Get a specific company note by company ID and note ID - `autotask_search_company_notes` — Search for notes on a specific company. Iterating across many companies trips Autotask's API threshold — scope the parent list first. - `autotask_create_company_note` — Create a new note for a company - `autotask_get_ticket_attachment` — Get a ticket attachment. With includeData=false (default) returns metadata only — fast, suitable for browsing. With includeData=true returns the base64 binary c - `autotask_search_ticket_attachments` — Search for attachments on a specific ticket. Each parent triggers a separate query — scope the parent ticket list before iterating. ## Install This entry has no npm package and no hosted endpoint, so there is nothing for an MCP client to launch or connect to. It is indexed as source only. ## Blast radius Extensive blast radius — deletes data; holds an api key. - Floor 45, ceiling 57 (tier: extensive) - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.WYRE-AI%2Fautotask-mcp - Install plan: https://forgeregistry.com/api/v1/packages/io.github.WYRE-AI%2Fautotask-mcp/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.WYRE-AI%2Fautotask-mcp - HTML page: https://forgeregistry.com/registry/io.github.WYRE-AI%2Fautotask-mcp - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.