Skybuffer

Showing 25 of 51 from the live probe.

• Get Checklist

  Retrieve all checklist items for a Redmine issue. Requires the RedmineUP Checklists plugin and ``REDMINE_CHECKLISTS_ENABLED=true``.

• Update Checklist Item

  Update a checklist item's text, done state, or position. Requires the RedmineUP Checklists plugin and ``REDMINE_CHECKLISTS_ENABLED=true``. This is a write operation and is blocked when ``REDMINE_MCP_READ_ONLY=true``.

• Create Checklist Item

  Create a new checklist item (or section header) on a Redmine issue. Requires the RedmineUP Checklists plugin and ``REDMINE_CHECKLISTS_ENABLED=true``. This is a write operation and is blocked when ``REDMINE_MCP_READ_ONLY=true``. Set ``is_section=True`` to create a bold section header with no checkbox.

• Manage Contact

  RedmineUP CRM (Contacts) plugin tool. Combined CRUD-by-action. Actions: ``list``, ``get``, ``create``, ``update``, ``delete``, ``assign_to_project``, ``remove_from_project``. Requires ``REDMINE_CRM_ENABLED=true`` and the RedmineUP CRM plugin.

• Manage Document

  Manage DMSF documents (list / get / create / update). Requires the ``redmine_dmsf`` plugin and ``REDMINE_DMSF_ENABLED=true``.

• List Redmine Trackers

  List all trackers (issue types) defined in the Redmine instance. Trackers classify issues (e.g., Bug, Feature, Support). Use this tool to discover valid ``tracker_id`` values before calling ``create_redmine_issue`` or ``update_redmine_issue``. Returns: A list of tracker dictionaries with ``id``, ``name``, and ``description``. On failure, a dict with an ``"error"`` key. Example: >>> await list_redmine_trackers() [ {"id": 1, "name": "Bug", "description": ""}, {"i

• List Redmine Issue Statuses

  List all issue statuses defined in the Redmine instance. Use this tool to discover valid ``status_id`` values before calling ``update_redmine_issue``. You can also pass a status name via the ``status_name`` field in ``update_redmine_issue``, which internally resolves the ID. Returns: A list of status dictionaries with ``id``, ``name``, and ``is_closed`` (whether this status counts as "closed"). On failure, a dict with an ``"error"`` key. Example: >>> await list_redmine_issue_s

• List Redmine Issue Priorities

  List all issue priority levels defined in the Redmine instance. Use this tool to discover valid ``priority_id`` values before calling ``create_redmine_issue`` or ``update_redmine_issue``. Returns: A list of priority dictionaries with ``id``, ``name``, ``active``, and ``is_default``. On failure, a dict with an ``"error"`` key. Example: >>> await list_redmine_issue_priorities() [ {"id": 1, "name": "Low", "active": True, "is_default": False}, {"id": 2, "name":

• List Redmine Users

  List Redmine users with optional filtering. Admin permission is required to list all users. Non-admin users may receive a 403. Use this tool to discover valid user IDs (e.g., for assignment, watchers, or time-entry authoring).

• Get Current User

  Retrieve the currently authenticated user's profile. Resolves to ``GET /my/account.json`` under the hood. Works for any authenticated user (not admin-only). Useful when an LLM needs to identify "me" — for example, when a user says "log 2h on this issue for me", the LLM can call this tool to get the current user's ID. Returns: A dictionary with ``id``, ``login``, ``firstname``, ``lastname``, ``mail``, ``admin`` (bool), ``created_on``, and ``last_login_on``. On failure, a dict with a

• List Redmine Queries

  List all saved custom queries visible to the current user. Custom queries are saved issue filters (defined via the Redmine web UI). Once discovered, the ``id`` can be passed to ``list_redmine_issues`` via a ``query_id`` filter to run the query. Note: This tool only READS queries. Redmine's REST API does not support creating, updating, or deleting saved queries. Returns: A list of query dictionaries with ``id``, ``name``, ``is_public``, and ``project_id`` (may be ``None`` for cross

• Get Redmine Attachment

  Download a Redmine attachment and return a usable reference to it. Downloads the attachment to local disk and returns either an HTTP URL (when the server has a publicly reachable hostname configured) or an absolute local file path (in stdio mode). The caller does not need to know which mode is active. **HTTP mode** (any explicit ``PUBLIC_HOST``, or a non-loopback ``SERVER_HOST``): Returns a dict with ``uri``, ``uri_type: "http"``, filename, content_type, size, expires_at, and attachment_id. An

• List Files

  List all files uploaded to a Redmine project. Returns file metadata (id, filename, size, content type, description, download URL, author, optional version/release) for every file uploaded under Project > Files. Note: This lists files from Redmine's core "Files" module (enabled per project via Settings > Modules > Files). It does NOT list issue attachments (use ``get_redmine_issue`` with ``include_attachments=True`` for those) and does NOT list DMSF documents (pending separate tools).

• Upload File

  Upload a file to a Redmine project's Files section. **Content sources — provide exactly ONE of:** - ``source_url``: an HTTP(S) URL the server will download from. Use this when chaining with another MCP tool that returns a download URL (e.g., a Google Drive MCP's ``get_drive_file_download_url``), when the file is hosted on the public web, or when the file is served by another local MCP server over localhost. **Prefer this over content_base64** when a URL is available — no need to do

• Delete File

  Delete a file from a Redmine project. **Important:** Redmine's ``DELETE /attachments/{id}.json`` endpoint removes ANY attachment by ID, not just project files. If ``file_id`` refers to an issue/wiki attachment (e.g., from ``get_redmine_issue(include_attachments=True)``), that attachment will be deleted from its issue. To avoid accidentally removing issue attachments when you meant to remove a project file, the tool verifies the target attachment is project-scoped (its ``container_type`` is ``P

• Get Gantt Chart

  Retrieve project timeline (Gantt) data: issues with dates, dependencies, and milestones. Composite tool that aggregates ``GET /issues.json`` (with relations) and ``GET /projects/{id}/versions.json`` into a single structured response suitable for timeline analysis. Returns structured data, not an image. Use cases: "What's the current timeline for project X?", "Which issues are overdue?", "Show me the dependency chain on this project". Uses the core Redmine REST API only — no plugin required.

• Get Redmine Issue

  Retrieve a specific Redmine issue by ID. Fetch issue details, view a ticket, show a bug report, get issue with comments, journals, attachments, or related metadata. Use this tool to pull a single issue with full context: comments (journals), attachments, custom fields, watchers, relations, subtasks/children, and (when ``REDMINE_AGILE_ENABLED=true``) agile metadata. For listing or filtering across multiple issues see ``list_redmine_issues``; for text search across issues see ``search_redmine_iss

• List Redmine Issues

  List Redmine issues with flexible filtering and pagination support. A general-purpose tool for listing issues from Redmine. Supports filtering by project, status, assignee, tracker, priority, and any other Redmine issue filter. Use this to list all issues in a project, find unassigned issues, or apply any combination of filters.

• Search Redmine Issues

  Search Redmine issues matching a query string with pagination support. Performs text search across issues using the Redmine Search API (/search.json), then transparently hydrates the matching ids via /issues.json so structured fields (subject, status, priority, project, assigned_to, author, timestamps) are populated in the response. The follow-up fetch is skipped when ``fields`` only requests id and/or description, which /search.json can serve on its own. Supports server-side pagination to pre

• Create Redmine Issue

  Create a new issue in Redmine. Open a ticket, file a bug, submit a feature request, log a support case, or report a task. Use this tool to create a single issue with a subject and optional description, plus any standard or custom fields (``tracker_id``, ``status_id``, ``priority_id``, ``assigned_to_id``, ``fixed_version_id``, ``parent_issue_id``, ``start_date``, ``due_date``, custom field values, etc.). For duplicating an existing issue see ``copy_issue``; for editing an existing issue see ``up

• Update Redmine Issue

  Update an existing Redmine issue. In addition to standard Redmine fields, a ``status_name`` key may be provided in ``fields``. When present and ``status_id`` is not supplied, the function will look up the corresponding status ID and use it for the update. When ``REDMINE_AGILE_ENABLED=true``, a ``story_points`` key may also be provided in ``fields``; it is routed to the RedmineUP Agile plugin endpoint separately and is not passed to the standard Redmine update. When ``REDMINE_AGILE_ENABLED=fals

• Copy Issue

  Duplicate an existing Redmine issue with optional field overrides. Uses Redmine's native copy mechanism (``copy_from`` parameter) which preserves the original issue's fields while allowing selected overrides.

• Manage Issue Relation

  List, create, or delete a Redmine issue relation.

• List Subtasks

  List subtasks (child issues) of a given Redmine issue. Retrieves all issues whose ``parent_issue_id`` equals the given ``issue_id``. To create a new subtask, use ``create_redmine_issue`` with the ``parent_issue_id`` field set.

• Delete Redmine Issue

  Hard-delete an issue via ``DELETE /issues/{id}.json``. Issue deletion in Redmine is **irreversible** and cascades to the issue's children (subtasks), journals (comments), attachments, time entries, and inbound relations from issues that referenced it. To prevent accidental destruction, this tool refuses unless the caller passes ``confirm_delete=True``; the refusal envelope includes a structured ``impact`` preview (counts of cascaded items) so a caller can decide whether to proceed. If the issu