genat-mcp 2.2.3 → 2.2.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/index.js +2 -2
  2. package/package.json +1 -1
  3. package/rules/genat-mcp.mdc +4 -0
package/index.js CHANGED
@@ -52,7 +52,7 @@ function insecureHttpsFetch(url, { method = 'GET', headers = {}, body }) {
52
52
  const server = new McpServer(
53
53
  {
54
54
  name: 'GenAT',
55
- version: '2.2.3',
55
+ version: '2.2.4',
56
56
  },
57
57
  {
58
58
  capabilities: {
@@ -65,7 +65,7 @@ server.registerTool(
65
65
  'GenAT',
66
66
  {
67
67
  description:
68
- 'Generate accessibility tests for a URL based on the project folder. Analyzes the page (DOM + a11y), detects project framework (TypeScript, JavaScript, or Python, BDD, Page Object), and returns generated test files (feature, spec/step defs, page objects). Optionally write files to the project folder. On failure: run node node_modules/genat-mcp/run-genat.mjs (NOT run-genat.mjs in project root). Use webhook-genat-login in N8N_WEBHOOK_URL (never webhook-genat).',
68
+ 'Generate accessibility tests for a URL based on the project folder. Analyzes the page (DOM + a11y), detects project framework (TypeScript, JavaScript, or Python, BDD, Page Object), and returns generated test files (feature, spec/step defs, page objects). Optionally write files to the project folder. IMPORTANT: When the user mentions a JIRA ticket (e.g. "JIRA RB-40039"), pass jiraNumber with the key only (e.g. RB-40039) so the workflow can fetch acceptance criteria. On failure: run node node_modules/genat-mcp/run-genat.mjs (NOT run-genat.mjs in project root). Use webhook-genat-login in N8N_WEBHOOK_URL (never webhook-genat).',
69
69
  inputSchema: {
70
70
  url: z.string().describe('Page URL to analyze for accessibility (e.g. https://example.com)'),
71
71
  parentProjectFolder: z
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "genat-mcp",
3
- "version": "2.2.3",
3
+ "version": "2.2.4",
4
4
  "mcpName": "io.github.asokans@oclc.org/genat",
5
5
  "description": "MCP server GenAT: generate accessibility tests via n8n workflow (url + project folder)",
6
6
  "type": "module",
package/rules/genat-mcp.mdc CHANGED
@@ -27,3 +27,7 @@ Example:
27
27
  ```bash
28
28
  N8N_WEBHOOK_URL='https://your-n8n/webhook-test/webhook-genat-login' N8N_INSECURE_TLS=1 node node_modules/genat-mcp/run-genat.mjs https://example.com .
29
29
  ```
30
+
31
+ ## When invoking GenAT with JIRA
32
+
33
+ When the user mentions a JIRA ticket in their prompt (e.g. "JIRA RB-40039", "JIRA ticket PROJ-123", "JIRA RB-40039"), **always pass `jiraNumber`** to the GenAT tool with the extracted key only (e.g. `RB-40039`, not "JIRA RB-40039"). The workflow uses this to fetch acceptance criteria. If you omit it, jiraNumber will be null and JIRA integration will not run.