redmine_request
Execute any Redmine REST API call directly, bypassing validation and workflow checks. Supports all HTTP methods with custom paths, body, and parameters.
Instructions
ESCAPE HATCH — generic passthrough to any Redmine REST endpoint.
Bypasses redmine-mcp's validation, workflow checks, and schema cache.
Every response carries validation_skipped: true so the caller
can't accidentally forget. Gated behind
REDMINE_MCP_ENABLE_PASSTHROUGH=true — calls return
passthrough_disabled if the flag isn't set.
Args:
method: HTTP verb. One of GET, POST, PUT, DELETE,
PATCH. Case-insensitive.
path: must start with /. Joined onto REDMINE_URL by the
client. Example: "/custom_fields.json".
body: body for POST/PUT/PATCH. Accepted as either a JSON-encoded
string (e.g. '{"issue": {"subject": "renamed"}}') or a
JSON object passed directly (e.g. {"issue": {"subject": "renamed"}}). Empty string / empty dict means no body.
(The dual form is intentional — some MCP transports auto-parse
JSON-shaped string args into objects before the tool sees them.)
params: query params for GET, in the same dual string/object form.
Honors REDMINE_MCP_READ_ONLY for non-GET methods.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | ||
| path | Yes | ||
| method | Yes | ||
| params | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |