MuninX MCP Server

Installation

Connect to https://api.muninx.com/mcp as a remote Streamable HTTP MCP server using a personal MuninX API token.

For Codex, set the token and register the server:

export MUNINX_API_TOKEN='muninx_pat:token-id:secret'
codex mcp add muninx --url https://api.muninx.com/mcp --bearer-token-env-var MUNINX_API_TOKEN

Smithery is an optional OAuth-based setup path for users who prefer registry-managed connection flows.

Configuration

Prerequisites are a MuninX account, a personal API token, and an MCP-compatible client such as Codex.

Authentication uses the Authorization: Bearer <token> header. The token should be stored in MUNINX_API_TOKEN for direct client setup.

Capabilities

MuninX MCP lets authenticated users inspect tickets, create and update tickets, read and create ticket messages, search visible support history, draft replies, and query ticket analytics.

Access is scoped to the MuninX user who created the token, so tenant, role, and ticket visibility rules still apply.

Limitations

MuninX does not currently offer a knowledge base or live chat, and fully autonomous AI agents are not available yet.

Closed tickets are permanently locked and cannot be updated or reopened. AI tools require the appropriate AI-assisted workflow or permissions, depending on whether you are using the in-app AI features or external MCP access.

References

• Docs: https://docs.muninx.com/
• MCP setup: https://docs.muninx.com/integrations/muninx-mcp/
• Smithery: https://docs.muninx.com/integrations/smithery/
• Authentication: https://docs.muninx.com/api/authentication/
• Capabilities: https://docs.muninx.com/reference/capability-matrix/
• Limitations: https://docs.muninx.com/reference/known-limitations/
• Troubleshooting: https://docs.muninx.com/reference/troubleshooting/
• Privacy: https://docs.muninx.com/reference/privacy-and-data-handling/
• Pricing: https://docs.muninx.com/reference/pricing-reference/