@dpesch/mantisbt-mcp-server 1.10.0 → 1.10.1

package/.github/workflows/ci.yml

@@ -0,0 +1,32 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Type check
+        run: npm run typecheck
+
+      - name: Build
+        run: npm run build
+
+      - name: Test
+        run: npm test

package/CHANGELOG.md

@@ -7,6 +7,19 @@ This project adheres to [Semantic Versioning](https://semver.org/).
 
 ---
 
+## [1.10.1] – 2026-05-02
+
+### Added
+- GitHub Actions CI workflow (`.github/workflows/ci.yml`): runs on push and pull requests to `main`; steps are typecheck, build, and test on Node.js 20.
+
+### Changed
+- Improved descriptions for `upload_file` and `list_issue_files`: both now include return shape, usage guidelines, and cross-references to related tools.
+
+### Fixed
+- `upload_file`: removed Zod `.refine()` calls from `inputSchema`. MCP SDK 1.27.x serialized `ZodEffects` (the type produced by `.refine()`) to an empty `properties: {}` object, making all parameters invisible to clients. Imperative validation in the handler is unchanged — the same constraints are still enforced at runtime.
+
+---
+
 ## [1.10.0] – 2026-04-11
 
 ### Added

package/dist/tools/files.js

@@ -15,7 +15,9 @@ export function registerFileTools(server, client, uploadDir) {
     // ---------------------------------------------------------------------------
     server.registerTool('list_issue_files', {
         title: 'List Issue File Attachments',
-        description: 'List all file attachments of a MantisBT issue.',
+        description: `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.`,
         inputSchema: z.object({
             issue_id: z.coerce.number().int().positive().describe('Numeric issue ID'),
         }),
@@ -42,13 +44,15 @@ export function registerFileTools(server, client, uploadDir) {
     // ---------------------------------------------------------------------------
     server.registerTool('upload_file', {
         title: 'Upload File Attachment',
-        description: `Upload a file as an attachment to a MantisBT issue via multipart/form-data.
+        description: `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.
+
+Two input modes — exactly one must be provided:
+- file_path: absolute path to a local file; filename is derived from the path automatically
+- content: Base64-encoded file content; filename must be supplied explicitly via the filename parameter
 
-Two input modes (exactly one must be provided):
-- file_path: absolute path to a local file — filename is derived from the path automatically
-- content: Base64-encoded file content — filename must be supplied explicitly via the filename parameter
+The optional content_type sets the MIME type (e.g. "image/png"); defaults to "application/octet-stream". Use the optional description to annotate the attachment.
 
-The optional content_type parameter sets the MIME type (e.g. "image/png"). If omitted, "application/octet-stream" is used.`,
+Use this tool to attach files such as logs, screenshots, or patches to an existing issue. To list existing attachments, use list_issue_files. To retrieve issue details, use get_issue.`,
         inputSchema: z.object({
             issue_id: z.coerce.number().int().positive().describe('Numeric issue ID'),
             file_path: z.string().min(1).optional().describe('Absolute path to the local file to upload (mutually exclusive with content)'),
@@ -56,12 +60,6 @@ The optional content_type parameter sets the MIME type (e.g. "image/png"). If om
             filename: z.string().min(1).optional().describe('File name for the attachment (required when using content; overrides the derived name when using file_path)'),
             content_type: z.string().optional().describe('MIME type of the file, e.g. "image/png" (default: "application/octet-stream")'),
             description: z.string().optional().describe('Optional description for the attachment'),
-        }).refine(d => !!(d.file_path ?? d.content), {
-            message: 'Either file_path or content must be provided',
-        }).refine(d => !(d.file_path && d.content), {
-            message: 'Only one of file_path or content may be provided',
-        }).refine(d => !d.content || !!d.filename, {
-            message: 'filename is required when using content',
         }),
         annotations: {
             readOnlyHint: false,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dpesch/mantisbt-mcp-server",
-  "version": "1.10.0",
+  "version": "1.10.1",
   "mcpName": "io.github.dpesch/mantisbt-mcp-server",
   "description": "MCP server for MantisBT REST API – read and manage bug tracker issues",
   "author": "Dominik Pesch",

package/server.json

@@ -3,12 +3,12 @@
   "name": "io.github.dpesch/mantisbt-mcp-server",
   "title": "MantisBT MCP Server",
   "description": "MantisBT MCP server – manage issues, notes, files, tags, and relationships. With semantic search.",
-  "version": "1.10.0",
+  "version": "1.10.1",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "@dpesch/mantisbt-mcp-server",
-      "version": "1.10.0",
+      "version": "1.10.1",
       "runtimeHint": "npx",
       "transport": {
         "type": "stdio"