Skip to main content
Glama
tiflux

TiFlux MCP Server

Official
by tiflux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to TiFlux MCP Server

No user-submitted related servers found.

    Related Servers

    • rt-mcp

      ghidav
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Request Tracker REST2 API, enabling ticket, queue, user, and asset management via natural language.
      MIT

    • mcp-ticketing-server

      ShaiviBansal
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for ticketing automation that exposes tools to create, search, and update IT helpdesk tickets, with metrics tracking.
      -
    • 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

    • 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-centreon

      fredriksknese
      F
      license
      A
      quality
      C
      maintenance
      MCP server for Centreon IT monitoring that enables querying host/service status, managing acknowledgements and downtimes, and retrieving performance metrics via natural language.
      17
      -
    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 31 tools

    Disambiguation4/5

    Most tools have distinct purposes, with clear prefixes and context. Some potential confusion exists between list_tickets and get_ticket, and between get_chat and list_*_chats, but the descriptions are detailed enough to differentiate.

    Naming Consistency4/5

    Predominantly follows verb_noun pattern (e.g., create_ticket, get_ticket, list_tickets). Minor deviations include 'search_catalog_item' instead of 'find_catalog_item' and 'get_ticket_stages_slas' with an irregular plural, but overall consistent.

    Tool Count3/5

    31 tools is on the higher end but justifiable for a comprehensive ticketing and chat system. Some tools are very specific (e.g., list_entity_field_options), which might add unnecessary complexity for basic use cases.

    Completeness4/5

    Covers most lifecycle operations for tickets and chats, including search and customization. Missing delete_ticket and direct client/user management tools, but the core workflows are well-supported.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources