# Jira Service Management alternatives for AI agents

2 alternatives to Jira Service Management. 2 have an interface an agent can drive. 2 are open source.

Page: alternatives/jira-service-management.html

## GLPI

ITIL service desk and asset manager with a Builder-documented REST API over every item type.

- Listing: apps/glpi-project--glpi.html
- JSON: apps/glpi-project--glpi.json
- License: GPL-3.0
- Agent interface: API, from the builder
- Reach: 7 of 10 jobs
- Last activity: 2026-09-02
- Effort: config-only
- Agent cannot reach: Run inventory from endpoints; Build dashboards and reports; Install plugins and configure entities
- Use it when: we are an MSP or internal IT team and want tickets, assets, and contracts in one place that our agent can query and update through a stable API
- Use it when: we need ITIL-style incident, problem, and change records rather than a chat-first support inbox
- Gotcha: REST API is disabled by default and needs an app token plus IP allowlist under Setup > General > API
- Gotcha: IT-helpdesk flavour: customer-facing support (chat, social channels) is not native
- Gotcha: GPL-3.0 copyleft; PHP 8.2+ and MariaDB 10.6+ required
- Gotcha: Official REST API v1 is being superseded by a High-Level API in GLPI 11; endpoint paths may change

## Request Tracker

Enterprise ticket tracker with a Builder-shipped MCP server for search, create, reply, and update.

- Listing: apps/bestpractical--rt.html
- JSON: apps/bestpractical--rt.json
- License: GPL-2.0
- Agent interface: MCP server, from the builder
- Reach: 6 of 10 jobs
- Last activity: 2026-09-01
- Effort: config-only
- Agent cannot reach: Dashboards, charts, and reports; Track assets (RT Assets); Configure scrips and automation; Knowledge base articles
- Use it when: we run a shared support or IT queue by email and want tickets triaged, assigned, and answered from our agent without leaving RT's audit trail
- Use it when: we already have an RT instance and want Claude or Cursor to search TicketSQL and draft replies as a named user
- Gotcha: MCP server needs RT 6.0+ with REST 2.0 enabled; older RT 4.x/5.x installs must upgrade first
- Gotcha: Everything the agent does is logged as the token's user, including emails sent on replies; a repeated add_reply sends mail again
- Gotcha: Perl stack with a long CPAN dependency install; SELinux default blocks /opt/rt6
- Gotcha: GPL-2.0 copyleft on both RT and the MCP server

## Questions

### Is there an open source alternative to Jira Service Management?

Yes. Both listings here are open source: GLPI (GPL-3.0), Request Tracker (GPL-2.0).

### Which Jira Service Management alternatives have an MCP server?

Request Tracker has an MCP server from its builder.

### Which Jira Service Management alternative can an agent do the most with?

GLPI: 7 of 10 recorded jobs reachable. Jobs differ by listing, so read each list before you choose.