Is this the same tool that creates an issue?

On GitHub, yes. issue_write both creates and updates; supply an existing issue number and it edits rather than opens. Jira and Gitea split the two, with a dedicated edit tool. Either way, this page is the update intent. Opening a fresh issue lives on the create page.

What can an agent change on an existing issue?

State, assignee, labels, and the body, on most of these. An agent closes a ticket when its branch merges, reassigns a stale bug, or relabels by triage rule. Jira goes broadest, editing arbitrary fields on the ticket, including custom ones a project defines.

MCP servers that can update an issue

3 verified servers expose a tool that can update an issue

Most of an issue's life happens after it is filed. The status moves, the assignee changes, a label gets added, someone rewrites a vague body once they understand the bug. Updating an issue is that edit path: change the fields on a ticket that already exists.

These verified servers let an agent update an issue on a repository or tracker, distinct from opening a new one.

Top pick

GitHub

Official

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

version-control30,334

Tool:

issue_write

On GitHub the same tool creates and updates: issue_write edits an existing issue, changing its state, labels, assignees, or body once it already has a number.

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:

editJiraIssue

editJiraIssue updates the fields on an existing Jira ticket, so an agent can move status, reassign, or rewrite a field without touching the rest of the issue.

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:

edit_issue

Gitea runs the same edit on a forge you host yourself: edit_issue changes an existing issue's fields on a self-hosted instance.

What to know

The update is where issue automation gets useful. An agent that closes a ticket when its branch merges, reassigns a stale bug, or relabels by triage rule is editing state, not creating it. The servers here expose that edit a little differently. GitHub and Gitea write changes onto an existing issue, the state, the labels, the body, the assignee. Jira updates fields on a ticket already in a project. The common move is the same: name the issue, supply the fields to change, leave the rest alone. On GitHub the same tool both creates and updates, so the update intent is just a write against an issue that already has a number.

This is also where an agent benefits from remembering what it last changed. Relabeling or closing a ticket twice is noise in the activity log, and worse, a reopened issue an agent then re-closes looks like a fight. Knowing the state it last set keeps the edits idempotent across sessions.

Questions

Is this the same tool that creates an issue?: On GitHub, yes. issue_write both creates and updates; supply an existing issue number and it edits rather than opens. Jira and Gitea split the two, with a dedicated edit tool. Either way, this page is the update intent. Opening a fresh issue lives on the create page.
What can an agent change on an existing issue?: State, assignee, labels, and the body, on most of these. An agent closes a ticket when its branch merges, reassigns a stale bug, or relabels by triage rule. Jira goes broadest, editing arbitrary fields on the ticket, including custom ones a project defines.