Can an agent filter, or does it get every issue?

Filter. GitHub and Gitea take state, label, and assignee filters; Jira takes a full JQL query, which can express conditions a simple filter cannot. An agent asks for just the open bugs labeled urgent, for example, rather than pulling the whole backlog.

Is a Sentry issue the same thing?

No. Sentry and other error trackers use issue to mean an aggregated error group, not a ticket a person filed. This page covers tracker issues, the work items in GitHub, Jira, and Gitea. Error groups are a separate capability built on a monitoring server.

MCP servers that can list issues

3 verified servers expose a tool that can list issues in a tracker

Triage starts with seeing the list. Before an agent works a backlog, finds duplicates, or reports on what is open, it needs to list the issues and read their state, filtered down to the ones that matter.

These verified servers let an agent list the issues on a repository or project.

Top pick

GitHub

Official

GitHub's official remote MCP server for repos, issues, pull requests, Actions, and code search.

version-control30,334

Tool:

list_issues

list_issues returns a repository's issues filtered by state, label, and assignee, the broad starting point for triage and reporting on GitHub.

Pick 2

Atlassian (Jira & Confluence)

Atlassian

Official

Atlassian's official remote MCP server for Jira and Confluence: read, search, create, and update issues and pages.

project-management746

Tool:

searchJiraIssuesUsingJql

searchJiraIssuesUsingJql runs a JQL query against Jira, so an agent can express almost any slice of a project, far past a simple state filter.

Pick 3

Gitea

Official

Gitea's official MCP server for repos, branches, issues, pull request reviews, releases, Actions, and wikis on any Gitea instance.

version-control73

Tool:

list_repo_issues

list_repo_issues lists a repository's issues on a self-hosted Gitea instance, the same triage read on a forge you run yourself.

What to know

A filtered issue list is the entry point for most backlog automation: the open bugs, the ones tagged a certain way, the stale ones nobody has touched. The trackers here take different query styles. GitHub and Gitea filter by state, label, and assignee on a repository. Jira goes further with JQL, a query language that can express almost any slice of a project. The shape that comes back is the same: issues with titles, states, and metadata the agent can reason over.

Error trackers like Sentry also call their groups issues, which is a different thing: an aggregated error, not a filed ticket. This page is about the tracker kind, the work items a person opened. An agent triaging a backlog also benefits from remembering what it already read, so a second pass does not re-scan the same hundred issues to find the five that changed.

Questions

Can an agent filter, or does it get every issue?: Filter. GitHub and Gitea take state, label, and assignee filters; Jira takes a full JQL query, which can express conditions a simple filter cannot. An agent asks for just the open bugs labeled urgent, for example, rather than pulling the whole backlog.
Is a Sentry issue the same thing?: No. Sentry and other error trackers use issue to mean an aggregated error group, not a ticket a person filed. This page covers tracker issues, the work items in GitHub, Jira, and Gitea. Error groups are a separate capability built on a monitoring server.