Checklists plugin and AI Agent integration

• What the AI gets

This article describes how the Checklists plugin works with the Redmine Agent plugin. Everything below needs the Agent plugin installed; without it Checklists works as usual. All data and actions follow the permissions of the user and, for MCP, the scopes of the OAuth token. See MCP server and AI assistant tools for general setup.

Available in Light and PRO.

What the AI gets

• Context of an issue: the checklist items of the issue (subject, done flag, section flag, position) are visible to the model for users with View checklists.
• MCP: get_issue, create_issue and update_issue return checklists and accept checklists_attributes, an array in the REST API shape: items without id are added, items with id are updated, _destroy: true removes one. subject is required for every item, also when updating. The argument is offered to users with Edit checklists or Done checklists in the project.
• The OAuth application must tick view_checklists, edit_checklists and done_checklists for clients to read and change checklists.

Example prompt for a client: "add a checklist with the steps of the release to issue #456 and mark the first step as done".