zopkit-bug-resolution-mcp 1.1.0 → 1.2.0

package/README.md

@@ -1,7 +1,7 @@
 # bug-resolution MCP server
 
-A two-tool MCP server so Claude Code (or Cursor, or any other MCP client) can
-work a Zopkit bug report end to end as native tool calls, instead of
+A four-tool MCP server so Claude Code (or Cursor, or any other MCP client)
+can work a Zopkit bug report end to end as native tool calls, instead of
 hand-rolling curl commands:
 
 - **`fetch_bug_context`** — pulls the full report (title, description,
@@ -11,8 +11,13 @@ hand-rolling curl commands:
 - **`submit_bug_resolution`** — writes back how it was fixed as a Markdown
   writeup and moves the report to `resolved`, via
   `POST /api/admin/bug-reports/resolution/:id`.
+- **`fetch_assigned_bugs`** — lists reports currently assigned to the API
+  key's owner ("what's on my plate"), optionally filtered by status, via
+  `GET /api/admin/bug-reports/assigned`.
+- **`create_bug_report`** — files a new bug report (plain-text description),
+  optionally self-assigning it, via `POST /api/admin/bug-reports/report`.
 
-Both are thin wrappers — see `backend/src/features/bug-reports/README.md`
+All four are thin wrappers — see `backend/src/features/bug-reports/README.md`
 for what each endpoint actually does server-side.
 
 Published to npm as
@@ -89,6 +94,14 @@ whoever asked you to fix it).
    and a Markdown writeup. It sets the report's resolution notes to that
    writeup and moves its status straight to `resolved`.
 
+Two more, independent of the fetch/resolve flow above:
+
+- Ask it to call `fetch_assigned_bugs` (optionally with a `status` filter) to
+  see what's currently assigned to you — no id needed.
+- Ask it to call `create_bug_report` with a `title` and plain-text
+  `description` to file something it noticed — pass `assignToSelf: true` to
+  claim it immediately.
+
 ## Notes
 
 - Not part of the pnpm workspace (`pnpm-workspace.yaml`) or the deployed
@@ -98,6 +111,6 @@ whoever asked you to fix it).
   via the `BUG_REPORT_API_KEY` env var, never embedded.
 - The key is per-developer and individually revocable from the same API Keys
   panel — revoking one never affects any other person's key.
-- This server only exposes the two operations it needs. It can't list or
-  search bug reports — the person/tool using it needs the report's id
-  already.
+- `fetch_bug_context` and `submit_bug_resolution` still need a report id —
+  this server doesn't search or browse. `fetch_assigned_bugs` is the one tool
+  that doesn't require knowing an id up front.

package/index.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-// bug-resolution MCP server — two tools wrapping the bug-reports resolution
+// bug-resolution MCP server — four tools wrapping the bug-reports resolution
 // API (see backend/src/features/bug-reports/README.md) so a developer's
 // Claude Code / Cursor session can work a bug report end to end as native
 // tool calls instead of hand-rolling curl commands:
@@ -8,6 +8,10 @@
 //     inline screenshot as real image content.
 //   - submit_bug_resolution: POST /api/admin/bug-reports/resolution/:id —
 //     writes back the fix as a Markdown resolution and marks it resolved.
+//   - fetch_assigned_bugs: GET /api/admin/bug-reports/assigned — "what's on
+//     my plate", always the API key owner's own assigned reports.
+//   - create_bug_report: POST /api/admin/bug-reports/report — file a new bug
+//     the tool found, optionally self-assigning it.
 // Thin wrapper: all the actual logic (auth, scoping, the DB writes) lives
 // server-side; this just forwards the HTTP calls the README documents.
 //
@@ -25,7 +29,11 @@ if (!API_KEY) {
     'Generate one from the company-admin panel (Bug Reports → API Keys) and set it when registering this server.');
 }
 
-const server = new McpServer({ name: 'zopkit-bug-resolution', version: '1.1.0' });
+const server = new McpServer({ name: 'zopkit-bug-resolution', version: '1.2.0' });
+
+const BUG_SEVERITIES = ['low', 'medium', 'high', 'critical'];
+const BUG_STATUSES = ['open', 'in_progress', 'blocked', 'further_discussion', 'resolved'];
+const BUG_PROJECTS = ['wrapper', 'crm', 'fa', 'accounting', 'academy', 'itsm', 'studio'];
 
 const IMG_SRC = /<img\b[^>]*\bsrc="([^"]+)"[^>]*>/gi;
 
@@ -189,5 +197,115 @@ server.registerTool(
   }
 );
 
+server.registerTool(
+  'fetch_assigned_bugs',
+  {
+    title: 'Fetch bugs assigned to me',
+    description:
+      "List Zopkit bug reports currently assigned to this API key's owner — \"what's on my plate\". " +
+      'Always the key owner\'s own assigned reports, never anyone else\'s, regardless of what the key ' +
+      'can otherwise see. Optionally filter by status.',
+    inputSchema: {
+      status: z.enum(BUG_STATUSES).optional().describe('Only return reports in this status.'),
+    },
+  },
+  async ({ status }) => {
+    if (!API_KEY) {
+      return {
+        isError: true,
+        content: [{ type: 'text', text: 'BUG_REPORT_API_KEY is not set on this MCP server — see README.md.' }],
+      };
+    }
+
+    const url = new URL(`${BASE_URL}/api/admin/bug-reports/assigned`);
+    if (status) url.searchParams.set('status', status);
+
+    let res;
+    try {
+      res = await fetch(url, { headers: { 'X-API-Key': API_KEY } });
+    } catch (err) {
+      return {
+        isError: true,
+        content: [{ type: 'text', text: `Could not reach ${BASE_URL}: ${err instanceof Error ? err.message : String(err)}` }],
+      };
+    }
+
+    const body = await res.json().catch(() => null);
+
+    if (!res.ok) {
+      const message = body?.message || body?.error || `HTTP ${res.status}`;
+      return { isError: true, content: [{ type: 'text', text: `Failed to fetch assigned bugs: ${message}` }] };
+    }
+
+    const reports = body?.data || [];
+    if (reports.length === 0) {
+      return { content: [{ type: 'text', text: 'No bug reports currently assigned to you.' }] };
+    }
+
+    const summary = reports
+      .map((r) => `- [${r.severity}/${r.status}] ${r.title} (id: ${r.id})${r.project ? ` — project: ${r.project}` : ''}`)
+      .join('\n');
+
+    return { content: [{ type: 'text', text: `${reports.length} assigned report(s):\n${summary}` }] };
+  }
+);
+
+server.registerTool(
+  'create_bug_report',
+  {
+    title: 'Create a bug report',
+    description:
+      'File a new Zopkit bug report — e.g. something this tool noticed while working on something else. ' +
+      'Description is plain text (paragraphs separated by a blank line), not rich-text HTML.',
+    inputSchema: {
+      title: z.string().min(1).max(255).describe('A short, specific summary of the bug.'),
+      description: z.string().min(1).describe('The bug, in plain text — what happened, expected vs actual, repro steps.'),
+      severity: z.enum(BUG_SEVERITIES).optional().describe('Defaults to "medium".'),
+      project: z.enum(BUG_PROJECTS).optional().describe('Which product this bug is in, if known.'),
+      pageUrl: z.string().max(2048).optional().describe('The URL where the bug was observed, if applicable.'),
+      assignToSelf: z.boolean().optional().describe('Self-assign this report to the API key owner. Defaults to false (unassigned).'),
+    },
+  },
+  async ({ title, description, severity, project, pageUrl, assignToSelf }) => {
+    if (!API_KEY) {
+      return {
+        isError: true,
+        content: [{ type: 'text', text: 'BUG_REPORT_API_KEY is not set on this MCP server — see README.md.' }],
+      };
+    }
+
+    let res;
+    try {
+      res = await fetch(`${BASE_URL}/api/admin/bug-reports/report`, {
+        method: 'POST',
+        headers: { 'Content-Type': 'application/json', 'X-API-Key': API_KEY },
+        body: JSON.stringify({ title, description, severity, project, pageUrl, assignToSelf }),
+      });
+    } catch (err) {
+      return {
+        isError: true,
+        content: [{ type: 'text', text: `Could not reach ${BASE_URL}: ${err instanceof Error ? err.message : String(err)}` }],
+      };
+    }
+
+    const body = await res.json().catch(() => null);
+
+    if (!res.ok) {
+      const message = body?.message || body?.error || `HTTP ${res.status}`;
+      return { isError: true, content: [{ type: 'text', text: `Failed to create bug report: ${message}` }] };
+    }
+
+    const report = body?.data;
+    return {
+      content: [{
+        type: 'text',
+        text: report
+          ? `Bug report created: "${report.title}" (id: ${report.id}).`
+          : 'Bug report created.',
+      }],
+    };
+  }
+);
+
 const transport = new StdioServerTransport();
 await server.connect(transport);

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "zopkit-bug-resolution-mcp",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "type": "module",
-  "description": "MCP server for Zopkit wrapper bug reports: fetch full bug context (with screenshots) and submit how a bug was fixed. Requires a BUG_REPORT_API_KEY (generated in the company-admin panel) — see README.md.",
+  "description": "MCP server for Zopkit wrapper bug reports: fetch full bug context (with screenshots), submit how a bug was fixed, list bugs assigned to you, and file new bug reports. Requires a BUG_REPORT_API_KEY (generated in the company-admin panel) — see README.md.",
   "license": "UNLICENSED",
   "engines": {
     "node": ">=18"