Skip to main content
Glama
JM-Addington

Autotask Search

by JM-Addington

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AUTOTASK_API_KEYYesYour API key for authentication
AUTOTASK_API_BASE_URLNoBase URL for the API (default: http://localhost:8000)http://localhost:8000

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_ticketsA

Search Autotask tickets using advanced semantic and keyword search with sentiment filtering and pagination.

This tool uses a sophisticated multi-method search combining:

  • BM25 full-text search

  • Semantic vector search

  • Fuzzy matching for typos

  • AI-powered reranking for relevance

  • Sentiment analysis filtering

  • Redis caching for fast pagination

get_ticket_detailsA

Get complete details for a specific ticket including all notes.

Use this tool when you need full information about a specific ticket, including the complete description and all human-created notes. This provides more context than search results alone.

get_tickets_detailsA

Get complete details for multiple tickets including all notes and time entries.

This tool fetches full ticket information for multiple tickets in a single request. More efficient than calling get_ticket_details multiple times when you need details for several tickets.

get_related_ticketsA

Find tickets semantically related to a given ticket using vector similarity and AI re-ranking.

This tool finds tickets that are similar in content, topic, or issue type by:

  1. Using vector embeddings to find semantically similar tickets

  2. Re-ranking results with an AI model for optimal relevance

  3. Returning the most related tickets with relevance scores

This is useful for:

  • Finding similar issues or tickets

  • Discovering patterns across related tickets

  • Finding tickets that might share the same root cause

  • Research and analysis of ticket trends

get_tickets_notesA

Get notes for multiple tickets in bulk.

Retrieve all human-created notes for specified tickets. You can provide either task IDs, ticket numbers, or both. This is more efficient than calling get_ticket_details multiple times when you only need the notes.

search_companiesA

Search for companies (accounts) in Autotask.

This tool searches the Autotask companies/accounts database using various matching strategies. It's useful for finding company information, looking up account IDs for filtering other searches, or exploring the customer base.

search_contactsA

Search for contacts (account contacts) in Autotask.

This tool searches the Autotask contacts database. It's useful for finding contact information, looking up contact IDs for filtering ticket searches, or exploring contacts associated with a specific company.

get_tickets_companyA

Get all tickets assigned to one or more companies.

This tool retrieves tickets that are formally assigned to the specified companies in the Autotask system. Use this after finding companies with search_companies.

Results are returned in reverse chronological order (newest first) without any search ranking or filtering applied.

get_tickets_contactA

Get all tickets assigned to one or more contacts.

This tool retrieves tickets that are formally assigned to the specified contacts in the Autotask system. Use this after finding contacts with search_contacts.

Results are returned in reverse chronological order (newest first) without any search ranking or filtering applied.

get_queuesA

Get ticket queues (categories) from Autotask.

Queues are used to categorize and route tickets in Autotask. Each ticket is assigned to exactly one queue. This tool retrieves the list of available queues for reference when filtering or categorizing tickets.

Note: "Queues" in the Autotask UI are called "TicketCategories" in the API. Both terms refer to the same entity.

get_tickets_by_queueA

Get all tickets in a specific queue with optional filtering.

This tool retrieves tickets from a specific queue (TicketCategory in Autotask). By default, only open/active tickets are returned (status != Complete). Use include_completed=True to include completed tickets.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JM-Addington/mcp-autotask-search'

If you have feedback or need assistance with the MCP directory API, please join our Discord server