targetprocess-mcp-server 2.1.7 → 2.1.8-a
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/README.md +15 -8
- package/build/index.js +2 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -56,8 +56,15 @@ Cards — Read
|
|
|
56
56
|
Cards — Write
|
|
57
57
|
- `add_comment` — Post a comment to any card (id, comment)
|
|
58
58
|
- `create_bug` — Create a standalone bug (title, bugContent, optional origin)
|
|
59
|
-
|
|
60
|
-
|
|
59
|
+
> `origin` accepted values: `Production - Customer`, `Production - Internal`, `Pre-Release - Customer`, `Pre-Release - Internal`, `Regression - Dev01`, `Regression - Team Env`, `Manual QA` *(default)*, `Developer Raised`, `Operations`
|
|
60
|
+
> [!NOTE]
|
|
61
|
+
> requires `TP_PROJECT_ID`, `TP_TEAM_ID`
|
|
62
|
+
- `create_bug_based_on_card` — Create a bug linked to an existing user story or bug card (card object with id+type, title, bugContent, optional origin)
|
|
63
|
+
> [!NOTE]
|
|
64
|
+
> requires `TP_PROJECT_ID`, `TP_TEAM_ID`
|
|
65
|
+
- `create_test_plan` — Create a test plan linked to a UserStory, Bug, or Feature (title, resourceId, optional resourceType, optional description/startDate/endDate)
|
|
66
|
+
> [!NOTE]
|
|
67
|
+
> requires `TP_PROJECT_ID`,
|
|
61
68
|
|
|
62
69
|
Test Case Workflows
|
|
63
70
|
- `write_test_cases` — Fetch a card (UserStory, Bug, or Feature) by ID and trigger the full test case writing workflow: Claude analyzes the card, generates detailed test cases covering happy path, edge cases, and error scenarios, creates a linked test plan via `create_test_plan`, then calls `add_test_cases_to_test_plan`. Each test case description contains Preconditions and Test Type as HTML; steps are passed as a structured array (resourceId, optional resourceType)
|
|
@@ -72,7 +79,7 @@ Teams
|
|
|
72
79
|
User
|
|
73
80
|
- `get_logged_in_user` — Get the currently logged-in user's info (no params needed)
|
|
74
81
|
|
|
75
|
-
|
|
82
|
+
|
|
76
83
|
---
|
|
77
84
|
|
|
78
85
|
## Installation
|
|
@@ -89,7 +96,7 @@ User
|
|
|
89
96
|
"TP_TOKEN": "<your-tp-token>" // Settings -> Authentication and Security -> New Access Token,
|
|
90
97
|
"TP_BASE_URL": "<tp-api-endpoint>",
|
|
91
98
|
"TP_OWNER_ID": "<tp-owner-id>", // your user id
|
|
92
|
-
"TP_PROJECT_ID": "<tp-project-id>"
|
|
99
|
+
"TP_PROJECT_ID": "<tp-project-id>"
|
|
93
100
|
"TP_TEAM_ID": "<tp-team-id>"
|
|
94
101
|
}
|
|
95
102
|
}
|
|
@@ -111,10 +118,10 @@ User
|
|
|
111
118
|
],
|
|
112
119
|
"env": {
|
|
113
120
|
"TP_TOKEN": "<your-tp-token>" // Settings -> Authentication and Security -> New Access Token,
|
|
114
|
-
"TP_BASE_URL": "<tp-api-endpoint>",
|
|
115
|
-
"TP_OWNER_ID": "<tp-owner-id>", // your user id
|
|
116
|
-
"TP_PROJECT_ID": "<tp-project-id>",
|
|
117
|
-
"TP_TEAM_ID": "<tp-team-id>"
|
|
121
|
+
"TP_BASE_URL": "<tp-api-endpoint>", // required
|
|
122
|
+
"TP_OWNER_ID": "<tp-owner-id>", // required, your user id
|
|
123
|
+
"TP_PROJECT_ID": "<tp-project-id>", // optional see available tools
|
|
124
|
+
"TP_TEAM_ID": "<tp-team-id>" // optional see available tools
|
|
118
125
|
}
|
|
119
126
|
}
|
|
120
127
|
},
|
package/build/index.js
CHANGED
|
@@ -335,7 +335,8 @@ server.registerTool('get_release_open_user_stories', {
|
|
|
335
335
|
server.registerTool('search_tp_cards', {
|
|
336
336
|
title: 'Search TP cards by keyword or phrase in description',
|
|
337
337
|
description: `Searches TP cards (UserStories or Bugs) by keyword or phrase or partial keyphrase in Card Description e.g. "Text Element", "Font field"
|
|
338
|
-
NOTE: after results are returned, try analyze and filter results by most relevant to what user is looking for in the description text
|
|
338
|
+
NOTE: after results are returned, try analyze and filter results by most relevant to what user is looking for in the description text
|
|
339
|
+
FALLBACK: if no results are found, try spliting phrase by spaces and searching for each word`,
|
|
339
340
|
inputSchema: {
|
|
340
341
|
keyword: z.string()
|
|
341
342
|
.describe('Keyword or partial name or keyphrase to search for in description'),
|