Jira Alerts (JSM Operations) MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add jira-alerts-mcp -- npx -y jira-alerts-mcp

{
  "mcpServers": {
    "jira-alerts-mcp": {
      "args": [
        "-y",
        "jira-alerts-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.jira-alerts-mcp]
command = "npx"
args = ["-y", "jira-alerts-mcp"]

{
  "mcpServers": {
    "jira-alerts-mcp": {
      "args": [
        "-y",
        "jira-alerts-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "jira-alerts-mcp": {
      "args": [
        "-y",
        "jira-alerts-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: JSM_CLOUD_ID (Atlassian site cloud id (a UUID). Find it at https://<your-site>.atlassian.net/_edge/tenant_info), JSM_EMAIL (Atlassian account email, for API token auth. Required unless JSM_OAUTH_TOKEN is set.), JSM_API_TOKEN (Atlassian account API token, paired with JSM_EMAIL. Required unless JSM_OAUTH_TOKEN is set.), JSM_OAUTH_TOKEN (OAuth 3LO or Forge bearer token. Takes precedence over JSM_EMAIL and JSM_API_TOKEN.). The author declared them in the registry entry; get the values from the project itself.