Skip to main content
Glama
WYRE-AI

Autotask MCP Server

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Autotask MCP Server

No user-submitted related servers found.

    Related Servers

    • ConnectWise API Gateway MCP

      jasondsmith72
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that provides a comprehensive interface for interacting with the ConnectWise Manage API, simplifying API discovery, execution, and management for both developers and AI assistants.
      7 npm
      18
      -

    • ServiceNow MCP Server

      LokiMCPUniverse
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants and development tools to interact with ServiceNow instances, providing comprehensive API coverage for incident management, change management, CMDB, and other ServiceNow modules.
      3
      MIT

    • OpenCTI MCP Server

      DarkAngel-agents
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that connects AI assistants to OpenCTI threat intelligence platforms. It enables natural language interaction for searching threat intelligence, analyzing reports, managing indicators, and monitoring connectors.
      -

    • ServiceNow MCP Server

      michaelbuckner
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server enabling AI agents to access and manipulate ServiceNow data through natural language interactions, allowing users to search for records, update them, and manage scripts.
      48
      MIT

    • KikoBooks MCP Server

      AccountantInc
      A
      license
      Not graded
      quality
      B
      maintenance
      A Model Context Protocol server for KikoBooks enterprise bookkeeping software that enables AI assistants to perform accounting operations on accounts, customers, invoices, bills, and more through natural language.
      1,117 npm
      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

    B3/5.0

    Scored across 98 tools

    Disambiguation3/5

    Tools are mostly entity-scoped (get_/search_/create_/update_/delete_), but the sheer volume and some near-duplicates (e.g., get_ticket_details vs search_ticket_history, service_call_ticket association vs service_call CRUD) can confuse. The meta tool list_categories is also odd in a flat toolset.

    Naming Consistency4/5

    Naming is predominantly consistent with an autotask_<verb>_<entity> pattern. Minor inconsistencies: list_* vs search_* (list_phases, list_categories) and get_ticket_details vs get_ticket_history where 'details' is vague.

    Tool Count2/5

    98 tools is far beyond the practical limit for MCP usability. Even for a broad PSA platform, the count will overwhelm context windows and decision-making. Several tools are narrowly scoped (e.g., search_service_call_tickets) and could be merged or split more judiciously.

    Completeness3/5

    The surface covers many core entities (tickets, companies, projects, service calls, quotes, billing), but significant gaps exist: no update/delete for notes or attachments, no update/delete for tasks or projects, no search/get for service calls (only create/delete/link), and opportunities/products/contracts are read-only.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources