MCP for Redmine · RedminePRO Docs

Q: Write tools are missing from the list.

Read-only mode is on, or Allow issue writes is off. Both also refuse the call directly.

Point Claude Desktop, Claude Code, Cursor or any Model Context Protocol client at your workspace and it can search, read, create, update and comment on issues, as a real person, with that person's exact permissions. Every read goes through the same visibility rules the web interface uses and every write through the same workflow and field rules, with the owner of the API key as the actor. The feature adds one capability: whether you may connect a client at all. It never widens what is behind it.

Client setup is covered separately in connecting an MCP client.

What you can do

Availability: Plus and above.
Trying it first: The RedminePRO demo workspace has MCP switched on whatever the price list says, so you can point a real client at a real workspace before you buy anything.
Turn it on: On by default once available.
Who may connect: A new workspace starts closed, Only these people, with nobody named.
Settings: A switched-off tool vanishes from the tool list and is refused if called anyway, with the same answer an invented name gets.
Using it: Name the people or groups who may connect, under Who may connect.
How people connect: Two ways, and both are supported.
Who is connected, and disconnecting: Each person sees their own connected clients under My account, with a Disconnect beside each.
Reading logged time: A client can read hours that have already been logged, your own, or a project's, and it sees exactly what the Spent time tab shows that person, because it asks the same question Redmine does.
Assigning to a person: A client can name an assignee by login, by full name in either order, or by user id, whichever way round your workspace displays names.

The MCP switches, throttle and plan state — From a live RedminePRO workspace.

Configure

Settings, permissions, modules and how to use it on RedminePRO Cloud.

Includes connecting Model Context Protocol clients.

Install on your own Redmine

Requirements, install, update and remove, for a self-hosted Redmine 6.

Common questions

The client says it is unauthorized.

The key is missing, wrong, or belongs to a locked account. Keys are per person; copying a colleague's is not a fix.

The client connects but every call is refused.

One of three things, and the message says which: the endpoint is switched off, the plan does not allow it, or the account is not named under Who may connect, and on a new workspace nobody is, until somebody is added.

Write tools are missing from the list.

Read-only mode is on, or Allow issue writes is off. Both also refuse the call directly.