mcp-sentinel-qa 2.0.1 → 2.0.2

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.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,19 @@
1
1
  # Changelog
2
2
 
3
+ ## 2.0.2 — 2026-10-29
4
+
5
+ ### Multi-level functionality hierarchy
6
+
7
+ - Update tool schemas and guidance to support functionality trees at any depth.
8
+ - Allow any same-project functionality as a parent; Sentinel validates scope and
9
+ prevents self-parenting and cycles.
10
+ - Clarify that moving a node keeps its descendant subtree and test cases attached,
11
+ while deleting a node promotes direct children and preserves deeper descendants.
12
+ - Describe the paginated list as flat rows linked by `parent_id`.
13
+
14
+ Version 2.0.2 aligns the MCP guidance with the multi-level hierarchy deployed in
15
+ Sentinel production. It preserves the thirteen tool names and argument shapes.
16
+
3
17
  ## 2.0.1 — 2026-10-29
4
18
 
5
19
  ### Functionality management
package/README.md CHANGED
@@ -27,7 +27,7 @@ Add the following server entry to your MCP client's configuration:
27
27
  "mcpServers": {
28
28
  "sentinel": {
29
29
  "command": "pnpm",
30
- "args": ["dlx", "mcp-sentinel-qa@2.0.1"],
30
+ "args": ["dlx", "mcp-sentinel-qa@2.0.2"],
31
31
  "env": {
32
32
  "SENTINEL_API_KEY": "YOUR_SENTINEL_API_KEY"
33
33
  }
@@ -43,26 +43,26 @@ secret storage or environment-variable references, use those instead.
43
43
  For a manual launch, provide the key through your environment and run:
44
44
 
45
45
  ```sh
46
- pnpm dlx mcp-sentinel-qa@2.0.1
46
+ pnpm dlx mcp-sentinel-qa@2.0.2
47
47
  ```
48
48
 
49
49
  The process waits for MCP messages on stdin; it is not an interactive terminal UI
50
50
  or an HTTP server. The API endpoint is currently fixed to
51
51
  `https://sentinel-qa.vercel.app`; `SENTINEL_API_URL` is not supported.
52
52
 
53
- ## Tools in 2.0.1
53
+ ## Tools in 2.0.2
54
54
 
55
55
  The package provides thirteen tools:
56
56
 
57
57
  | Tool | Purpose |
58
58
  | --- | --- |
59
59
  | `sentinel_list_projects` | List projects available to the API key. Start here to obtain project IDs. |
60
- | `sentinel_list_functionalities` | List project functionalities with pagination and parent details. |
61
- | `sentinel_create_functionality` | Create a root or child functionality. |
60
+ | `sentinel_list_functionalities` | List flat, paginated functionality records with each node's immediate parent. |
61
+ | `sentinel_create_functionality` | Create a root or nested functionality at any depth. |
62
62
  | `sentinel_get_functionality` | Retrieve a functionality's details, project and parent. |
63
63
  | `sentinel_update_functionality` | Partially edit its name, description, color, status or parent. |
64
- | `sentinel_move_functionality` | Move a functionality under another root or promote it to a root. |
65
- | `sentinel_delete_functionality` | Delete a functionality while preserving its cases and children. |
64
+ | `sentinel_move_functionality` | Move a functionality branch under any same-project node or promote it to a root. |
65
+ | `sentinel_delete_functionality` | Delete a functionality while preserving cases and descendant hierarchy. |
66
66
  | `sentinel_move_functionality_test_cases` | Atomically transfer selected test cases to another functionality. |
67
67
  | `sentinel_list_test_cases` | Search and paginate test cases, with project, functionality, priority, status and type filters. |
68
68
  | `sentinel_get_test_case` | Retrieve a test case by UUID. |
@@ -74,13 +74,16 @@ Tool schemas expose required fields and allowed values. Test-case lists support
74
74
  `page` and `page_size` (maximum 100); functionality lists use the same pagination
75
75
  with a default page size of 20.
76
76
 
77
- Functionalities support a two-level root/child hierarchy. Parents must be roots
78
- in the same project. A functionality with children cannot become a child, and
79
- self-parenting or cycles are rejected. Editing preserves omitted fields. Moving
80
- a functionality changes its parent; moving test cases changes their assignment.
81
- Deleting a functionality unlinks its cases by default or transfers them to an
82
- active target when `target_id` is provided. Direct children become roots and keep
83
- their own cases.
77
+ Functionalities can be nested at any depth. `parent_id` identifies the immediate
78
+ parent, which may be any functionality in the same project; an omitted or null
79
+ parent creates or promotes a root. The paginated list is flat, so follow every
80
+ page to reconstruct the full hierarchy. Sentinel validates project scope and
81
+ rejects self-parenting or cycles, including moves under a node's own descendant.
82
+ Moving a functionality changes its parent while its descendants and test cases
83
+ stay attached. Moving test cases is a separate operation that changes their
84
+ assignment. Deleting a functionality unlinks its cases by default or transfers
85
+ them to an active target when `target_id` is provided. Direct children become
86
+ roots; deeper descendants remain attached to those children.
84
87
 
85
88
  Reading functionalities requires `features.view`; creation requires
86
89
  `features.create`; edits and hierarchy changes require `features.edit`. Case
@@ -114,11 +117,12 @@ replace it in your client configuration.
114
117
  ## Upgrade from 1.x
115
118
 
116
119
  Version 2.0.0 introduced the Node.js 22 minimum; Node.js 18 and 20 are not
117
- supported. Version 2.0.1 keeps that requirement and adds functionality management
118
- tools while preserving the existing eight tool names. Update a pinned
119
- `mcp-sentinel-qa@2.0.0` configuration to `mcp-sentinel-qa@2.0.1`, then restart or
120
- reconnect your MCP client. Older examples using `mcp-server-sentinel` should use
121
- `mcp-sentinel-qa` instead.
120
+ supported. Version 2.0.1 added functionality management tools while preserving
121
+ the existing eight tool names. Version 2.0.2 updates their hierarchy guidance to
122
+ match Sentinel's multi-level functionality tree without changing tool names or
123
+ arguments. Update a pinned `mcp-sentinel-qa@2.0.1` configuration to
124
+ `mcp-sentinel-qa@2.0.2`, then restart or reconnect your MCP client. Older
125
+ examples using `mcp-server-sentinel` should use `mcp-sentinel-qa` instead.
122
126
 
123
127
  ## Development and release checks
124
128
 
package/dist/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mcp-sentinel-qa",
3
- "version": "2.0.1",
3
+ "version": "2.0.2",
4
4
  "description": "MCP server for Sentinel QA — manage functionalities and test cases from any AI assistant",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -11,7 +11,7 @@ export function registerFunctionalityTools(server) {
11
11
  }
12
12
  function registerReads(server) {
13
13
  server.registerTool('sentinel_list_functionalities', {
14
- description: 'List project functionalities with parent_id and pagination. Follow pagination to see the complete two-level hierarchy.',
14
+ description: 'List project functionalities as flat, paginated rows. Each parent_id identifies the immediate parent; follow all pages to reconstruct the hierarchy at any depth.',
15
15
  inputSchema: listFunctionalitiesSchema,
16
16
  annotations: { readOnlyHint: true },
17
17
  }, ({ project_id, page = 1, page_size = 20 }) => toolRequest(() => api.get('/api/mcp/functionalities', {
@@ -20,32 +20,32 @@ function registerReads(server) {
20
20
  page_size: page_size?.toString(),
21
21
  })));
22
22
  server.registerTool('sentinel_get_functionality', {
23
- description: 'Get functionality details, including its project and parent. Read before editing or deleting.',
23
+ description: 'Get functionality details, including its project and immediate parent_id. Read before editing, moving or deleting.',
24
24
  inputSchema: getFunctionalitySchema,
25
25
  annotations: { readOnlyHint: true },
26
26
  }, ({ id }) => toolRequest(() => api.get(`/api/mcp/functionalities/${id}`)));
27
27
  }
28
28
  function registerCreate(server) {
29
29
  server.registerTool('sentinel_create_functionality', {
30
- description: 'Create a root or child functionality. parent_id must reference a root in the same project; omit it or use null for a root. Maximum depth is two levels.',
30
+ description: 'Create a root or nested functionality at any depth. parent_id may reference any functionality in the same project; omit it or use null for a root. Sentinel rejects cross-project parents and cycles.',
31
31
  inputSchema: createFunctionalitySchema,
32
32
  }, (params) => toolRequest(() => api.post('/api/mcp/functionalities', params)));
33
33
  }
34
34
  function registerUpdate(server) {
35
35
  server.registerTool('sentinel_update_functionality', {
36
- description: 'Partially edit name, description, color, status or parent_id. Omitted fields are preserved; null clears description/color or promotes to root. Cannot change project.',
36
+ description: 'Partially edit name, description, color, status or parent_id. Omitted fields are preserved; null clears description/color or promotes to root. A parent may be any node in the same project; Sentinel rejects cycles. Cannot change project.',
37
37
  inputSchema: updateFunctionalitySchema,
38
38
  }, ({ id, ...changes }) => toolRequest(() => api.patch(`/api/mcp/functionalities/${id}`, changes)));
39
39
  }
40
40
  function registerMove(server) {
41
41
  server.registerTool('sentinel_move_functionality', {
42
- description: 'Move a functionality under another root in the same project, or promote it with parent_id:null. A functionality with children cannot become a child. Test cases stay attached.',
42
+ description: 'Move a functionality branch under any node in the same project, or promote it with parent_id:null. Sentinel rejects moving a node under itself or one of its descendants. Descendants and test cases stay attached.',
43
43
  inputSchema: moveFunctionalitySchema,
44
44
  }, ({ id, parent_id }) => toolRequest(() => api.patch(`/api/mcp/functionalities/${id}`, { parent_id })));
45
45
  }
46
46
  function registerDelete(server) {
47
47
  server.registerTool('sentinel_delete_functionality', {
48
- description: 'Delete a functionality after confirming the target. Preserve all test cases: unlink them by default or transfer to target_id, an active functionality in the same project. Direct children become roots.',
48
+ description: 'Delete a functionality after confirming the target. Unlink its test cases by default or transfer them to target_id, an active functionality in the same project. Direct children become roots; deeper descendants remain attached to their parents.',
49
49
  inputSchema: deleteFunctionalitySchema,
50
50
  annotations: { destructiveHint: true },
51
51
  }, ({ id, target_id }) => toolRequest(() => api.del(`/api/mcp/functionalities/${id}${target_id ? `?target_id=${encodeURIComponent(target_id)}` : ''}`)));
@@ -9,7 +9,12 @@ const fields = {
9
9
  .optional()
10
10
  .describe('Hex color or null'),
11
11
  status: z.enum(['Ativa', 'Inativa']).describe('Functionality status'),
12
- parent_id: z.string().uuid().nullable().optional().describe('Root parent UUID; null for a root'),
12
+ parent_id: z
13
+ .string()
14
+ .uuid()
15
+ .nullable()
16
+ .optional()
17
+ .describe('Immediate parent UUID in the same project; omit or use null for a root. Any depth is supported.'),
13
18
  };
14
19
  export const listFunctionalitiesSchema = z
15
20
  .object({
@@ -49,7 +54,7 @@ export const moveFunctionalitySchema = z
49
54
  .string()
50
55
  .uuid()
51
56
  .nullable()
52
- .describe('New root parent UUID, or null to promote to root'),
57
+ .describe('Immediate parent UUID in the same project at any depth, or null to promote to root'),
53
58
  })
54
59
  .strict()
55
60
  .refine(({ id, parent_id }) => id !== parent_id, 'A functionality cannot be its own parent');
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mcp-sentinel-qa",
3
- "version": "2.0.1",
3
+ "version": "2.0.2",
4
4
  "description": "MCP server for Sentinel QA — manage functionalities and test cases from any AI assistant",
5
5
  "type": "module",
6
6
  "license": "MIT",