Redmine

Turn the REST API on first. It is off by default.

1. As an administrator go to Administration → Settings → API and tick Enable REST web service.
2. Open My account for the user the agent should act as; the API access key is in the right-hand sidebar. Show it and copy it.
3. Set REDMINE_URL to your instance root (no trailing slash) and REDMINE_API_KEY to the key.

The header is X-Redmine-API-Key. Redmine also accepts the key as a key= query parameter, but a header keeps it out of the web server's access log.

Permissions follow the user, per project role. A project the user is not a member of is absent from the results rather than an error, and a role without View issues produces an empty issue list on a project that is full of them.

Custom fields are a nested array. cf_5 filters on custom field 5; the values come back in a custom_fields array of {id, name, value}, not as top-level properties.

Issue filters are query parameters with Redmine's own operators: status_id=open|closed|*|<id>, assigned_to_id=me|<id>, created_on=><2026-01-01|2026-03-31 for a range, >=2026-01-01 for an open-ended one. project_id takes the numeric id or the project identifier string.

include fetches related data in one call. On an issue, include=journals,attachments,relations saves several round trips — journals are the comment history and are omitted by default because they can be long.

Paging is offset and limit (max 100), with total_count in the response body.

Self-hosted, which is the thing to plan for.

• On AnythingMCP Cloud the instance must be reachable from the public internet on a real hostname with a valid TLS certificate. A self-signed certificate will fail: the connector offers no trust-anything switch.
• On an internal host (redmine.intern, 10.0.0.x), self-host AnythingMCP on the same network and add that host to SSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.

Writes: redmine_add_issue_note posts a real note that notifies the issue's watchers.