Skip to main content
Glama
JM-Addington

Autotask Search

by JM-Addington
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Autotask Search

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

    • Autotask MCP Server

      ddurko1950
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with Autotask PSA through natural language, providing tools for ticket triage, time logging, company lookups, project management, and more.
      39 npm
      Apache 2.0

    • autotask

      jamesdeane2
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with AutoTask PSA data, supporting natural language ticket queries, updates, notes, and bulk export.
      MIT

    • Autotask MCP Server

      ddurko1950
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to directly query and manage Autotask PSA data through natural language, including ticket triage, time entry creation, company lookups, project management, billing review, and more.
      Apache 2.0
    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

    A4/5.0

    Scored across 11 tools

    Disambiguation3/5

    Some tools have overlapping purposes, particularly get_ticket_details, get_tickets_details, and get_tickets_notes, which all retrieve ticket information and notes. Names like 'get_tickets_details' and 'get_tickets_notes' could easily be confused, though descriptions help clarify the distinctions. The other retrieval tools (by company, contact, queue) are clearly distinct.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern with 'search' and 'get' prefixes. Minor inconsistencies exist: get_ticket_details is singular while get_tickets_details is plural, and 'get_tickets_by_queue' uses 'by' while 'get_tickets_company' and 'get_tickets_contact' do not. Overall, the pattern is predictable and readable.

    Tool Count5/5

    With 11 tools, the server is well-scoped for a search-oriented read-only API. Each tool serves a distinct retrieval purpose, and the count is within the ideal range of 3-15 tools.

    Completeness4/5

    The tool set provides a comprehensive read-only surface for ticket searching and retrieval, covering search by text, company, contact, queue, and related tickets, plus batch detail and notes retrieval. Minor gaps exist, such as no direct company/contact detail retrieval beyond search, but the core workflows are covered.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources