MuninX

Name: MuninX
Author: muninx

Connect your AI client to MuninX, the simple help desk for small teams. MuninX MCP lets authenticated users inspect tickets, create and update tickets, read and create ticket messages, search visible support history, draft replies for review, and query ticket analytics. Access stays scoped to the connected user’s MuninX tenant, role, and permissions.

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链

接入信息

传输形态: http
鉴权方式: 鉴权未知
端点: https://helpdesk--muninx.run.tools

鉴权方式未标注，请核对官方文档后再接入——不要直接使用以下片段

{
  "mcpServers": {
    "MuninX": {
      "url": "https://helpdesk--muninx.run.tools"
    }
  }
}

能力清单

工具	说明
create_message	Add a message to a ticket. Use type external for customer-facing replies and internal for support-team notes. Customer tokens cannot create internal messages. When new-status is omitted, the messages API derives the next ticket status from the actor role and message type.
create_ticket	Create a ticket with its initial message.
get_ticket	Get one visible ticket by ID. User-facing summaries should lead with the ticket title and key metadata, not the ID.
list_ticket_messages	List newest-first messages for a visible ticket. Customer tokens do not receive internal notes. When organization reply identity is enabled, customer-visible staff authors may be returned as the organization instead of the individual agent or admin.
list_tickets	List tickets visible to the Muninx API token owner within the authenticated tenant. Behavior depends on the token owner's role: customers cannot filter by creator or assignee; agents cannot filter by assignee and, unless participant is supplied, see tickets assigned to themselves; admins can use all filters. Do not combine creator and participant. For MCP input, state and priority must be arrays of enum values, not comma-separated strings. Use ticket titles and metadata for user-facing summaries; ticket IDs are mainly for follow-up tool calls.
query_ticket_analytics	Query authenticated tenant ticket analytics. The analytics API enforces tenant and role scoping: customers are scoped to their own created tickets and agents to assigned tickets. Use count for ticket counts and avg_resolution_time, avg_response_time, or avg_first_reply_time for time metrics returned in seconds. Dates support YYYY-MM-DD or relative day offsets like -30d. Filters are exact string matches except updated_at, which means include tickets updated after the supplied date or offset.
search_tickets	Search visible ticket content in the authenticated tenant. Returns grouped ticket IDs; use get_ticket for full ticket details. Set include-preview when short matched snippets would help the user understand why a ticket matched. For MCP input, filters.kind must be an array of enum values, not a comma-separated string.
update_ticket	Update mutable public fields on a ticket.

纠错与举报（发现条目失效、署名有误或涉及侵权？）

提交举报 / 纠错

侵权举报经核验成立后，我们会即时下线该条目并删除已存的内容副本。