MantisBT MCP Server

Return all field names that are valid for the "select" parameter of list_issues and get_issue. Fields are discovered by fetching a sample issue from MantisBT (which reflects the server's active configuration — e.g. whether eta, projection, or profile fields are enabled) and merging the result with fields that MantisBT omits when empty (notes, attachments, relationships, etc.). The result is cached with the same TTL as the metadata cache. Use this tool before constructing a "select" string to ensure you only request fields that exist on this server.

Retrieve multiple MantisBT issues by their numeric IDs in a single MCP call. Requests run in parallel (max 5 concurrent). Missing or inaccessible IDs return null at their array position — the call never fails due to individual missing IDs. Response includes "requested", "found", and "failed" counters for quick validation.

Returns the version of the connected MantisBT installation and optionally compares it against the latest official release on GitHub. The version is read from the X-Mantis-Version response header sent by every API call. The GitHub comparison requires an outbound HTTPS request to the GitHub API.

Returns the version of this mantisbt-mcp-server instance.

Return a compact summary of cached MantisBT metadata: project count, tag count, and per-project counts of users, versions, and categories. If the cache does not exist or has expired (default TTL: 24 hours), it will automatically sync first. Use sync_metadata to force a refresh. For full lists use: list_projects (projects), get_project_users / get_project_versions / get_project_categories (per-project data), list_tags (tags).

Return the complete raw MantisBT metadata cache: all projects with full fields, and per-project lists of users, versions, categories, plus all tags. If the cache does not exist or has expired (default TTL: 24 hours), it will automatically sync first. Use sync_metadata to force a refresh. For a lightweight overview use get_metadata instead.

List all categories available for a MantisBT project. Note: The MantisBT API returns global (cross-project) categories with a "[All Projects] " prefix. This tool strips that prefix so the returned names can be used directly when creating issues.

List all users with access to a specific MantisBT project. Returns an array of user objects, each containing id, name (login name), real_name, email, and access_level fields. Use get_project_users when you need the complete user list for a project — for example, to verify who has access or to build a handler list. For name-based lookup of a single user, prefer find_project_member which supports case-insensitive substring search and is significantly faster on large projects. Access level IDs: 10=viewer, 25=reporter, 40=updater, 55=developer, 70=manager, 90=administrator. Prerequisites: obtai…

List all versions defined for a MantisBT project. Returns an array of version objects, each containing id, name, released (boolean), obsolete (boolean), and timestamp (version date). To create, change, release or delete versions use create_version, update_version, release_version and delete_version. Use the returned version names directly when creating or updating issues via create_issue and update_issue (version, target_version, fixed_in_version fields). By default, obsolete and inherited parent-project versions are excluded. Set obsolete=true to include deprecated versions; set inherit=tru…

Returns the current fill level of the semantic search index: how many issues are indexed vs. the total number of issues in MantisBT, plus the timestamp of the last sync.

List all saved MantisBT issue filters accessible to the current user. Filter IDs can be used with list_issues.

List all file attachments of a MantisBT issue. Returns an array of attachment objects, each containing id, filename, size in bytes, content_type, and download_url. Returns an empty array if the issue has no attachments. Use this tool when you need to inspect or enumerate files attached to an issue. To add a new attachment, use upload_file instead. To retrieve full issue details that include attachments alongside other fields, use get_issue instead.

List MantisBT issues with optional filtering. Returns a paginated list of issues. Use the "select" parameter to limit returned fields and reduce response size significantly. Note: "assigned_to", "reporter_id", "status", and date filters are applied client-side (the MantisBT REST API does not support these as server-side filters). When any of these filters are active the tool automatically fetches multiple pages internally until enough matching results are found (up to 500 issues scanned). The "page" and "page_size" parameters refer to the resulting filtered list. Tip for date queries: fetchi…

List all languages supported by the MantisBT installation.

List all notes (comments) attached to a MantisBT issue. Note: get_issue already includes notes in its response — use list_notes only when you need notes without fetching the full issue.

List all MantisBT projects accessible to the current API user.

List all tags defined in the MantisBT installation. The MantisBT REST API exposes a GET /tags endpoint on some installations. If that endpoint is not available, this tool falls back to the local metadata cache populated by sync_metadata.

Build or update the semantic search index for MantisBT issues. Use full: true to clear the existing index and rebuild from scratch.

Mark a version as released and set its date (default: now). Optionally create a follow-up version in the same step. The follow-up version is only created when next_version is given; its name is used as-is — no automatic numbering. Returns { released: <version> } plus either next_version: <version> or next_version_error: <message>. The two steps are separate API calls: if creating the follow-up version fails, the release itself stays in effect and the error is reported in next_version_error. The version must belong to project_id itself: versions inherited from a parent project can only be ch…

Remove a user from the monitor list of a MantisBT issue. The user will no longer receive email notifications for updates to this issue.

Remove a relationship from a MantisBT issue. Use get_issue first to retrieve the relationship IDs. The relationship_id is the numeric id field of a relationship object in the issue's relationships array (not the type ID).

Search MantisBT issues using natural language. Returns the most relevant issues by semantic similarity. The search index must be populated first via rebuild_search_index.

Fetch all projects and their associated users, versions, categories, and tags from MantisBT and store them in the local metadata cache. Tags are fetched via the dedicated GET /tags endpoint when available. On installations where that endpoint is missing (MantisBT < 2.26), tags are collected by scanning all issues across all projects. This is useful for getting a complete overview of your MantisBT installation. The cache is valid for 24 hours by default (configurable via MANTIS_CACHE_TTL env var). Use this tool to refresh stale data.

Update one or more fields of an existing MantisBT issue using a partial PATCH. The "fields" object accepts any combination of: - summary (string) - description (string) - steps_to_reproduce (string) - additional_information (string) - status: { name: "new"|"feedback"|"acknowledged"|"confirmed"|"assigned"|"resolved"|"closed" } - resolution: { id: 20 } (20 = fixed/resolved) - handler: { id: <user_id> } or { name: "<username>" } - priority: { name: "<priority_name>" } - severity: { name: "<severity_name>" } - reproducibility: { name: "<reproducibility_name>" } - category: { name: "<category_nam…

Update an existing version of a MantisBT project. Only the fields you pass are changed. Returns the updated version object. Renaming a version also rewrites the version, target_version and fixed_in_version fields of all issues that reference it (including subprojects if versions are inherited). Setting released=true does not change the version date — pass timestamp as well, or use release_version, which does both. The version must belong to project_id itself: versions inherited from a parent project can only be changed via the parent's project_id (otherwise MantisBT answers "Version not fou…

Upload a file as an attachment to a MantisBT issue. Adds the file to the issue without modifying any issue fields or status. Returns the created attachment metadata on success. Provide exactly one of the two input modes: - file_path (preferred): absolute path to a local file — use this whenever the file exists on disk; the server reads and encodes it automatically; filename is derived from the path. Note: file_path reads from the server's filesystem and is disabled over the HTTP transport unless MANTIS_UPLOAD_DIR is configured — HTTP clients should use content instead. - content: Base64-encod…