Use MuninX with AI clients

The MuninX MCP server lets compatible AI clients interact with MuninX using your MuninX permissions. After setup, an AI client such as Codex can inspect tickets, create and update tickets, read and create ticket messages, search support history, draft replies, and query ticket analytics.

MCP access is scoped to the MuninX user who created the API token. Admins, agents, and customers may see different tickets or have different write permissions, including whether they can create tickets or post ticket messages.

How MCP differs from MuninX AI-assisted features

MuninX has built-in AI-assisted features inside the app for draft replies and response improvement. Those features are available only to admins and agents whose agent type is AI-assisted. MuninX pays the underlying AI usage cost for those in-app features as part of the AI-assisted agent subscription.

MuninX MCP is different. It is an integration interface for external AI clients, not the same thing as the in-app AI buttons. Any authenticated MuninX user with a personal API token can connect an MCP-compatible client, subject to the records and actions their MuninX role allows.

With MCP, the external AI client handles AI model usage and billing. MuninX provides the authenticated access to tickets, messages, search, and analytics; the person or organization using the external AI client is responsible for that AI client’s costs.

Prerequisites

Before connecting an AI client, you need:

• A MuninX account.
• A personal API token.
• An MCP-compatible client such as Codex.

If you prefer an OAuth-based setup through Smithery, see Use MuninX with Smithery.

Create an API token

MuninX MCP requests use personal API tokens. To create one:

1. Sign in to MuninX.
2. Open Settings and select the API Tokens tab.
3. Select Create token.
4. Enter a descriptive name for the AI client or integration.
5. Copy the token, store it securely, and select I have saved this token.

The raw token is shown only once. For more detail, including token revocation, see Authentication.

Connect Codex

Set your MuninX API token in an environment variable:

export MUNINX_API_TOKEN='muninx_pat:token-id:secret'

Register the MuninX MCP server with Codex:

codex mcp add muninx \
  --url https://api.muninx.com/mcp \
  --bearer-token-env-var MUNINX_API_TOKEN

Restart your Codex session after setting the environment variable. Run /mcp in Codex to confirm that the muninx server and its tools are available.

If you prefer to manage MCP servers in configuration, use this equivalent entry in ~/.codex/config.toml, or in .codex/config.toml for a trusted project:

[mcp_servers.muninx]
url = "https://api.muninx.com/mcp"
bearer_token_env_var = "MUNINX_API_TOKEN"

Connect Claude Code

Claude Code can connect to remote HTTP MCP servers with request headers. Set the same MuninX API token environment variable:

export MUNINX_API_TOKEN='muninx_pat:token-id:secret'

Then add a Claude Code MCP configuration that sends the token as a bearer token:

{
  "mcpServers": {
    "muninx": {
      "type": "http",
      "url": "https://api.muninx.com/mcp",
      "headers": {
        "Authorization": "Bearer ${MUNINX_API_TOKEN}"
      }
    }
  }
}

Use this JSON in a Claude Code MCP configuration file such as .mcp.json, or adapt it for your preferred Claude Code configuration scope. Restart Claude Code after setting the environment variable, then run /mcp to confirm that the muninx server is connected.

Claude app custom connectors, Claude Desktop, and Team or Enterprise connector settings may expose different setup flows. Use the MuninX MCP URL https://api.muninx.com/mcp and configure authentication as Authorization: Bearer <your MuninX API token> when the client supports custom headers or bearer-token authentication.

What AI clients can do

Connected AI clients can use the MuninX MCP server to:

• List, inspect, create, and update tickets.
• Read and create ticket messages.
• Search visible ticket content.
• Query ticket analytics.

The AI client still operates through MuninX permissions. MCP requests use the API token owner’s tenant and role. Customers do not see internal notes, and role-specific ticket access rules still apply.

Example prompts

Use natural language prompts that match the support workflow you want help with:

• “Which tickets created today need my attention first?”
• “Summarize today’s support workload by priority.”
• “Draft replies for the two most urgent tickets from today.”

When asking for drafts, review the response before sending it to a customer.

Keep tokens secure

Store your MuninX API token in an environment variable. Do not paste tokens into prompts, chat messages, screenshots, or configuration files committed to source control.

If a token may have been exposed, delete it from Settings > API Tokens and create a replacement.