Muninx

Muninx is a help desk for small teams. Connect it to ChatGPT to search support history, inspect and update tickets, create new tickets, draft customer replies, and understand ticket activity using natural language. Perfect for startups, agencies, and teams that have outgrown a shared inbox.

View in the ChatGPT registry

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Customer Support
Primary Subcategory: Helpdesk & Ticketing Platforms
Secondary Subcategories: None listed
Brand: MuninX
Access: Account required
First tracked: 2026-06-25
Tool count: 8
Geography: US

ChatGPT Plugin Discoverability Score

ChatGPT organic discovery is not live yet

Muninx is tracked in the ChatGPT Plugin registry. Public organic-discovery measurement is not live for ChatGPT yet, so there is no score to publish today.

Get notified when your score goes live

Enter your work email and we’ll notify you when ChatGPT Plugin organic discovery scoring launches.

No spam. Unsubscribe any time.

Talk to our team

Primary Subcategory

Competing in ChatGPT Helpdesk & Ticketing Platforms

View Category

Listed in alphabetical order

Primary Subcategory

Apna JobsOrganic discovery is pendingGet the score at launch

EasyReplyOrganic discovery is pendingGet the score at launch

MuninxOrganic discovery is pendingGet the score at launch

PylonOrganic discovery is pendingGet the score at launch

UnthreadOrganic discovery is pendingGet the score at launch

Score explained

How the Discoverability Score works

Organic discovery scoring for Muninx on ChatGPT is not live yet. The score will use measured agent conversations when it launches.

InvisibleBuriedEmergingCompetitiveWinning

Organic discovery scoring is pending. Your Plugin score will appear on this scale when measurement goes live.

FoundDiagnostic

Whether Claude found your Plugin in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.

PickedMain score

How often your Plugin appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.

PositionedDiagnostic

What position your Plugin appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.

Read the full scoring methodology Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.

Tools

8 tools agents can invoke

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 a ticket with its initial message.
Get one visible ticket by ID. User-facing summaries should lead with the ticket title and key metadata, not the ID.
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 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 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 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 mutable public fields on a ticket.

Muninx FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Muninx alternatives on ChatGPT?

As of 2026-08-14, Muninx competes with Apna Jobs, EasyReply, Pylon, Unthread in ChatGPT Helpdesk & Ticketing Platforms, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.