Redmine MCP server

What the model can do

Redmine projects, issues with tracker, status, assignee and dates, an issue's notes and history, time entries and full-text search; can also create, change, relate or delete issues, add notes, manage watchers, log, correct or delete time, create, change or delete versions, create, change, archive or delete projects, publish news, and add or remove project members when you ask.

Reads

• redmine_list_projectsRedmine projects the key's user can see: numeric id (the issue list needs it), identifier, name, parent and the start of the description.
• redmine_list_issuesRedmine issues, most recently updated first: id, subject, project, tracker, status, priority, author, assignee…
• redmine_get_issueOne Redmine issue in full with its relations to other issues and its journals: the notes people added and the field changes, oldest first…
• redmine_list_time_entriesTime logged in Redmine: date, hours, person, project, issue, activity and comment, with the total.
• redmine_searchFull-text search across Redmine: issues, wiki pages, news, documents, changesets and forum messages the user can see.
• redmine_list_membersMembers of a Redmine project with their user (or group) ids and roles, and the membership ids, for adding a watcher…
• redmine_list_rolesThe roles defined in Redmine (Manager, Developer, Reporter…) with their ids, for adding a project member.
• redmine_list_versionsVersions (releases, milestones) available in a Redmine project, including shared ones: id, name, status, due date…

Acts, when you ask

These change something in Redmine. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• redmine_create_issueCreate an issue in a Redmine project.
• redmine_add_noteAdd a note (comment) to a Redmine issue, as the key's user.
• redmine_log_timeLog time on a Redmine issue, as the key's user.
• redmine_update_issueChange an existing Redmine issue: subject, description, status, priority or assignee, optionally with a note saying why.
• redmine_delete_issueDELETE a Redmine issue with its notes, history, attachments and the time logged on it.
• redmine_delete_time_entryDELETE one Redmine time entry.
• redmine_update_time_entryCorrect a logged Redmine time entry (ids from redmine_list_time_entries): hours, the day, the activity, the comment, or the issue it is logged on.
• redmine_add_issue_relationRelate one Redmine issue to another: relates, duplicates, duplicated, blocks, blocked, precedes, follows (with an optional delay in days…
• redmine_delete_issue_relationRemove a relation between two Redmine issues by its id (redmine_get_issue lists an issue's relations).
• redmine_add_watcherAdd a person as a watcher of a Redmine issue (user id from redmine_list_members, only somebody the user named).
• redmine_remove_watcherStop a person watching a Redmine issue.
• redmine_create_versionCreate a version (a release or milestone) in a Redmine project.
• redmine_update_versionChange a Redmine version: name, description, due date, status (open, locked against new issues, or closed) or sharing.
• redmine_delete_versionDELETE a Redmine version.
• redmine_create_projectCreate a Redmine project, optionally as a sub-project.
• redmine_update_projectChange a Redmine project's name, description or homepage.
• redmine_archive_projectArchive or unarchive a Redmine project.
• redmine_delete_projectDELETE a Redmine project permanently with its sub-projects, issues, time entries, wiki, files and versions.
• redmine_create_newsPublish a news item in a Redmine project.
• redmine_add_memberChanges access.
• redmine_remove_memberChanges access.

Connect it

First connect Redmine on Dashboard → Connections, then add Memtro to your client once. The Redmine tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Redmine connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which open bugs in the Support project have no assignee?
• › What notes were added to issue 8812 this week?
• › How many hours did Dan Fletcher log in October?
• › Add a note to issue 8812 that the fix ships on Thursday
• › Close issue 8790 and assign it back to Priya Nair

Questions

Is this an official Redmine MCP server?

No. It is Memtro's MCP server with Memtro's Redmine connector behind it: the connector reads Redmine through its API with the credentials you connect on Dashboard → Connections, and Redmine publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Redmine?

Only when you ask, and only what it has been granted: create an issue in a project; add a note to an issue; log time on an issue; change an issue's subject, description, status, priority or assignee; delete an issue; delete a time entry; correct a logged time entry; relate two issues (blocks, precedes, duplicates and so on); remove a relation between issues; add a watcher to an issue; remove a watcher from an issue; create a version; change a version's name, due date, status or sharing; delete a version; create a project; change a project's name, description or homepage; archive or unarchive a project; delete a project and everything in it (permanent); publish a news item in a project; add a member to a project with roles; remove a member from a project. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server