Skip to main content
Glama
TICnine

Autotask MCP Server

by TICnine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Autotask MCP Server

No user-submitted related servers found.

    Related Servers

    • Autotask MCP Server

      haxos-anon
      A
      license
      B
      quality
      C
      maintenance
      Gives AI assistants direct access to Autotask PSA for searching tickets, creating time entries, managing companies, projects, and more via natural language.
      100
      Apache 2.0

    • ConnectWise Manage MCP Server

      sberlo9
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to work directly with ConnectWise Manage through natural conversation, offering tools to search and update tickets, log time, manage companies, contacts, projects, and more across cloud and self-hosted instances.
      Apache 2.0

    • SyncroMSP MCP Server

      advenimus
      A
      license
      C
      quality
      C
      maintenance
      Enables AI assistants to fully access and manage SyncroMSP resources including tickets, customers, assets, invoices, and over 30 resource types through 180+ API endpoints.
      100
      16 npm
      10
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 90 tools

    Disambiguation3/5

    Most tools are clearly separated by resource+action, and descriptions clarify parent entities such as ticket notes vs company notes. However, the list/search split, overlapping enum tools like list_ticket_statuses vs get_field_info, and the meta-tools (router, execute_tool, list_category_tools) create enough ambiguity that misselection is plausible.

    Naming Consistency4/5

    The autotask_ prefix and verb_noun structure are applied consistently across nearly all tools. The main deviations are mixing list and search for lookup operations and a few exceptions like get_ticket_details and execute_tool, but these are minor and predictable.

    Tool Count1/5

    With 90 tools, the surface far exceeds the recommended 3-15 range and matches the extreme mismatch threshold. The inclusion of router, category, and executor meta-tools suggests the design is compensating for an overly large tool set rather than being well-scoped.

    Completeness3/5

    Core workflows for tickets, projects, service calls, quotes, and charges are reasonably covered. However, many resources have create/get/search but no update or delete, including contacts, opportunities, tasks, phases, notes, time entries, and expense items, leaving notable dead ends.

    Resources