Skip to main content
Glama
jitbit

jitbit-helpdesk-mcp

Official
by jitbit
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

Related Servers

Alternatives to jitbit-helpdesk-mcp

No user-submitted related servers found.

    Related Servers

    • tickiti-mcp by tickiti

      tickiti-mcpofficial

      tickiti
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that exposes the Tickiti helpdesk API to AI assistants, enabling ticket management and helpdesk operations via natural language.
      11
      MIT

    • i-net HelpDesk MCP Server

      roddyst
      A
      license
      A
      quality
      B
      maintenance
      MCP server that exposes the i-net HelpDesk Ticket Web-API as tools for AI agents, enabling ticket search, reading, creation, and actions like replying, closing, and escalating, with attachment support.
      8
      MIT

    • freshservice-mcp

      mchluba
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with Freshservice service desk, supporting ticket search, retrieval, and creation via a configurable, Docker-first deployment.
      MIT

    • FS_MCP_thin

      cbreland-DLR
      F
      license
      B
      quality
      D
      maintenance
      A read-only MCP server that connects AI assistants to Freshservice Service Desk for ticket triage, asset analysis, and support history summarization.
      23
      -

    • servicedesk-plus

      kaattaalan
      A
      license
      A
      quality
      C
      maintenance
      MCP server for ManageEngine ServiceDesk Plus that lets AI agents list, search, create, update, and manage help desk tickets and technical notes in real-time.
      6
      MIT

    • MCP Server for Intercom

      raoulbia-ai
      A
      license
      A
      quality
      F
      maintenance
      An MCP-compliant server that enables AI assistants like Claude Desktop to access and analyze Intercom support tickets with full conversation history.
      4
      8
      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

    A3.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_ticket retrieves a single ticket with full details, list_tickets provides filtered listings with pagination, and search_tickets performs keyword-based searches. There is no overlap in functionality—an agent can easily choose the right tool based on whether they need a specific ticket, a filtered list, or a search.

    Naming Consistency5/5

    All tools follow a consistent jitbit_verb_noun pattern (jitbit_get_ticket, jitbit_list_tickets, jitbit_search_tickets). The naming is uniform, using snake_case throughout with clear verbs (get, list, search) that accurately describe each action.

    Tool Count3/5

    With only 3 tools, the server feels thin for a helpdesk domain that typically involves ticket management workflows. While the tools cover basic retrieval and listing, the count is borderline low for operations like creating, updating, or closing tickets, which are common in such systems.

    Completeness2/5

    The tool set is severely incomplete for a helpdesk server. It only provides read-only operations (get, list, search), with no ability to create, update, assign, or close tickets. This leaves significant gaps that will cause agent failures when trying to perform common helpdesk tasks beyond querying existing data.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources