Skip to content
Jira Service Management Operations logo

Jira Service Management Operations MCP server

Opsgenie alerts in Jira Service Management: create, acknowledge, close and route on-call alerts, and see who is on call.

Jira Service Management Operations is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
16
Works with
Any MCP client
Auth
Custom auth or Basic auth
License
MIT, open source
Updated
September 2026

About the Jira Service Management Operations MCP server

Connect Jira Service Management Operations once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Jira Service Management Operations and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Jira Service Management Operations tools your AI can run

Once connected, your assistant can call any of these Jira Service Management Operations actions by asking in plain language.

  • Create Alert

    Create a new alert and route it to teams, users or schedules.

    16 fields

  • Get Alert

    Get one alert by its ID or alias.

    2 fields

  • Find Alerts

    Search alerts with a JSM Operations search query.

    5 fields

  • Acknowledge Alert

    Acknowledge an alert so responders know someone is on it.

    5 fields

  • Unacknowledge Alert

    Put an acknowledged alert back to open.

    2 fields

  • Close Alert

    Close an alert once the problem is resolved.

    5 fields

  • Add Note to Alert

    Add a note to an alert.

    5 fields

  • Add Tags to Alert

    Add one or more tags to an alert.

    3 fields

  • Remove Tags from Alert

    Remove one or more tags from an alert.

    3 fields

  • Assign Alert

    Make a user the owner of an alert. Not available on the JSM Free plan.

    3 fields

  • Add Responder to Alert

    Add a team, user, schedule or escalation as a responder.

    4 fields

  • Escalate Alert

    Escalate an alert to the next level of an escalation policy.

    3 fields

  • Snooze Alert

    Pause notifications for an alert until a set time. Not on JSM Free.

    3 fields

  • Update Alert

    Change the message, description or priority of an alert.

    5 fields

  • Get Who Is On Call

    Get who is on call for a schedule, now or at a given time.

    2 fields

  • Custom API Call

    Call any JSM Operations endpoint with this connection.

    10 fields

Triggers

Jira Service Management Operations events your agent can watch

These start a run the moment something happens in Jira Service Management Operations, so work gets picked up on its own.

  • New Alert

    Triggers when a new alert is created.

    1 field

Give your assistant Jira Service Management Operations

Connect Jira Service Management Operations once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Jira Service Management Operations MCP, answered.

No. That is the point of it. One Activepieces server exposes Jira Service Management Operations alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Jira Service Management Operations in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 16 tools, including Create Alert, Get Alert, Find Alerts, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.