Connect your AI to Redmine

What your AI can do with Redmine

Once connected, these tools appear automatically in your AI assistant:

• list_issuesread-only

  List issues, filtered. Ids come from the lookup tools: list_projects, list_issue_statuses, list_trackers, list_project_members. Use `statusFilter` for the common open/closed cut rather than guessing status ids.

• get_issueread-only

  Get one issue in full: fields, custom fields, its journal (comments and every field change) and its relations. Custom fields come back as {id, name, value} — that is where to learn a custom field's id before writing it with update_issue.

• searchread-only

  Full-text search across the instance — issues, wiki pages, projects, documents. Use it when you do not know which project or resource holds the answer; use list_issues when you do.

• create_issuewrite · needs approval

  Create an issue. `projectId`, `trackerId` and `priorityId` come from list_projects, list_trackers and list_enumerations — a tracker must be enabled on the project or Redmine refuses the whole call. Writes to Redmine, so it goes through the confirmation guardrail when enabled.

• update_issuewrite · needs approval

  Update an issue's fields. Only what you pass changes. To add a comment without touching any field, use add_issue_note instead.

• add_issue_notewrite · needs approval

  Add a comment to an issue, changing nothing else. Set `private` for a note only visible to members with the right permission.

• list_issue_relationsread-only

  Relations of one issue — what it blocks, what blocks it, what it precedes, duplicates or relates to. The way to answer 'what is holding this up?'.

• create_issue_relationwrite · needs approval

  Relate two issues. `precedes` and `follows` accept a delay in days; the other types do not. Writes to Redmine.

• list_projectsread-only

  List the projects visible to this key, with their id, name and identifier.

• get_projectread-only

  Get one project with the trackers enabled on it and its issue categories — needed before creating an issue, since a tracker not enabled on the project is refused.

• list_project_membersread-only

  Who is on a project, with their user id and roles. This is how you turn a person's name into the id that assignedToId expects — Redmine's global user directory is administrator-only, this is not.

• list_trackersread-only

  Trackers of the instance (Bug, Feature, Support…), with their ids. A tracker must also be enabled on the target project — get_project says which are.

• list_issue_statusesread-only

  Issue statuses of the instance with their ids, and which of them count as closed.

• list_enumerationsread-only

  Enumerated values with their ids: issue priorities, time-tracking activities or document categories. Needed before creating an issue or logging time.

• list_time_entriesread-only

  Logged time, filterable by project, issue, user or date range.

• log_timewrite · needs approval

  Log time against an issue or a project. `activityId` comes from list_enumerations (kind time_entry_activities). Writes to Redmine.

• list_wiki_pagesread-only

  Index of a project's wiki: page titles, versions and parents.

• get_wiki_pageread-only

  Get one wiki page with its text and current version number — pass that version to update_wiki_page so a concurrent edit is refused rather than overwritten.

• create_wiki_pagewrite · needs approval

  Create a wiki page. Fails if the title already exists — use update_wiki_page for an existing one. Writes to Redmine.

• update_wiki_pagewrite · needs approval

  Replace a wiki page's text. Pass the `version` returned by get_wiki_page: Redmine then refuses the write if someone edited the page meanwhile, instead of silently discarding their work. Writes to Redmine.

Example prompts

Just ask your AI in plain language — it picks the right Redmine tool:

• “List issues, filtered. Ids come from the lookup tools: list_projects, list_issue_statuses, list_trackers, list_project_members. Use `statusFilter` for the common open/closed cut rather than guessing status ids — from Redmine, in plain language.”
• “Get one issue in full: fields, custom fields, its journal (comments and every field change) and its relations. Custom fields come back as {id, name, value} — that is where to learn a custom field's id before writing it with update_issue — from Redmine, in plain language.”
• “Full-text search across the instance — issues, wiki pages, projects, documents. Use it when you do not know which project or resource holds the answer; use list_issues when you do — from Redmine, in plain language.”
• “Relations of one issue — what it blocks, what blocks it, what it precedes, duplicates or relates to. The way to answer 'what is holding this up?' — from Redmine, in plain language.”

How it works

1. Create your Proxoria account and add your MCP endpoint to Claude or ChatGPT.
2. Connect Redmine with your API key — each user connects their own account, credentials encrypted at rest.
3. Your AI instantly gets the Redmine tools. Write actions wait for your approval in the dashboard before anything changes.

Frequently asked questions

Does Redmine have an official MCP server?

You don't need one. Proxoria exposes Redmine to your AI through the Model Context Protocol, so you can use it from Claude, ChatGPT, Mistral or any MCP-compatible client — no official Redmine MCP server required.

What can my AI do with Redmine through Proxoria?

It gets 20 tools: list_issues, get_issue, search, create_issue, update_issue, add_issue_note, list_issue_relations, create_issue_relation, list_projects, get_project, list_project_members, list_trackers, list_issue_statuses, list_enumerations, list_time_entries, log_time, list_wiki_pages, get_wiki_page, create_wiki_page, update_wiki_page. For example, list issues, filtered. ids come from the lookup tools: list_projects, list_issue_statuses, list_trackers, list_project_members. use `statusfilter` for the common open/closed cut rather than guessing status ids.

Is the Redmine connector read-only?

No — it can also make changes. Write actions go through Proxoria's confirmation guardrail by default: your AI proposes them, and you approve each one from your dashboard before anything is written to Redmine.

How do I connect Redmine to my AI?

Create a Proxoria account, connect Redmine with your API key, and add your Proxoria MCP endpoint to Claude or ChatGPT. Your AI instantly gains the Redmine tools.