Loading
Jira Alerts (JSM Operations)
io.github.rrvrsClaim this server
Power your agent
Add this server
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
Local command
npx -y [email protected]Credentials from the publisher
- 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.
Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
shClaude Code
JSM_CLOUD_ID=<value> JSM_EMAIL=<value> JSM_API_TOKEN=<secret> JSM_OAUTH_TOKEN=<secret> claude mcp add io.github.rrvrs-jira-alerts-mcp -- npx -y jira-alerts-mcp@2.1.1Run in a terminal.
jsonClaude Desktop
{ "mcpServers": { "io.github.rrvrs-jira-alerts-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "JSM_CLOUD_ID": "<value>", "JSM_EMAIL": "<value>", "JSM_API_TOKEN": "<secret>", "JSM_OAUTH_TOKEN": "<secret>" } } }}claude_desktop_config.json
Local · npmPublisher installStep-by-step: add this in Claude
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchServer facts
Local- Transport
- stdio
- Version
Tools
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ