Skip to main content
Glama
ThatDayneGuy

Autotask MCP Server

by ThatDayneGuy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Autotask MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      27 npm
      Apache 2.0

    • 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

    • 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

      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

      TICnine
      A
      license
      C
      quality
      C
      maintenance
      Provides AI assistants with direct access to Autotask PSA for MSP operations. Enables natural language interaction for ticket management, time logging, company lookups, project tracking, and billing review through 39 comprehensive tools.
      100
      27 npm
      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

    B3.3/5.0

    Scored across 98 tools

    Disambiguation5/5

    Each tool targets a distinct entity and action (e.g., autotask_create_ticket vs. autotask_search_tickets). Multiple 'search' tools exist but are clearly scoped to different resources. No two tools share an overlapping purpose.

    Naming Consistency5/5

    All tools follow the consistent pattern 'autotask_<verb>_<noun>', using standard verbs (create, update, delete, get, search, list) and clear entity names. Even meta-tools like autotask_list_categories fit the pattern.

    Tool Count4/5

    98 tools is high but aligned with the broad scope of the Autotask PSA platform, covering many entities and sub-resources. The count is justified for comprehensive API coverage, though it borders on heavy.

    Completeness3/5

    Major entities (tickets, projects, companies, contacts) have create, read, update, and search operations, but notable deletions are missing for main resources (e.g., no autotask_delete_ticket or autotask_delete_project). Sub-items have deletes, but core CRUD is incomplete.

    Resources