Skip to content

Use MuninX MCP through Smithery

Smithery is an MCP registry and connection platform. It helps users discover MCP servers, connect them to supported AI clients, and manage the connection lifecycle outside the client itself.

MuninX MCP is available on Smithery at smithery.ai/servers/muninx/muninx. This setup path is optional. You can still connect directly to the MuninX MCP server with a personal API token if you prefer to manage client configuration yourself.

Smithery can make MCP setup easier when you do not want to manually create a MuninX API token, store it in an environment variable, and configure bearer-token headers in each client.

According to the Smithery Connect documentation, Smithery provides a connection layer for MCP servers that can handle OAuth setup, token refresh, secure credential storage, and connection state. For MuninX users, that means Smithery can reduce manual token handling and provide a guided setup flow for supported clients.

Smithery can be useful if:

  • You want to find and install MuninX MCP from an MCP registry.
  • You prefer OAuth-based authorization over copying a personal API token into local client configuration.
  • You use a client that supports Smithery connection links or Smithery-managed MCP setup.
  • You want Smithery to manage the MCP connection lifecycle for you.

Smithery is a third-party connection layer. If your organization prefers to configure clients directly and keep token management outside Smithery, use the direct MuninX MCP setup instead.

Before connecting MuninX through Smithery, you need:

  • A MuninX account.
  • Access to the MuninX workspace data you want the AI client to use.
  • A Smithery account.
  • A Smithery-supported MCP client, or the Smithery CLI.

MuninX permissions still apply. The AI client can only access MuninX records and actions allowed for the MuninX user who authorizes the connection. Admins, agents, and customers may see different tickets or have different write permissions.

To connect MuninX through Smithery:

  1. Open the MuninX MCP listing on Smithery: smithery.ai/servers/muninx/muninx.
  2. Choose the supported client or connection method you want to use.
  3. Follow the Smithery setup flow for that client.
  4. When prompted, authorize Smithery to connect to your MuninX account.
  5. Return to your AI client and confirm that the MuninX MCP tools are available.

The exact labels and setup options may vary by client. For the current Smithery workflow, see the Smithery Connect documentation. If your client supports Smithery deep links, Smithery may be able to configure the MCP connection automatically; see Smithery deep linking for details.

After setup, you can ask your AI client questions such as:

  • “Which MuninX tickets need my attention today?”
  • “Summarize open high-priority tickets.”
  • “Draft a reply for the most urgent ticket.”

Review any drafted customer response before sending it.

Smithery also provides a command-line tool for searching, connecting, and managing MCP servers. The Smithery CLI documentation includes the current install and command reference.

At a high level:

Terminal window
npm install -g smithery@latest
smithery auth login
smithery mcp search "MuninX"
smithery mcp add muninx --id muninx
smithery tool list muninx

If Smithery returns an authorization URL during setup, open it, complete the MuninX authorization flow, then retry listing the tools.

Use direct MuninX MCP setup if you want to:

  • Configure Codex, Claude Code, or another MCP client yourself.
  • Use a personal MuninX API token directly.
  • Avoid adding a third-party connection layer between your AI client and MuninX.
  • Keep all MCP configuration in local or project-specific client config files.