targetprocess-mcp-server 1.0.21 → 1.0.22

package/README.md

@@ -58,6 +58,9 @@ Cards — Write
 - `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)
 - `create_test_plan` — Create a test plan linked to a user story (title, userStoryId)
 
+Projects
+- `get_projects` — Get all Targetprocess projects (no params needed)
+
 User
 - `get_logged_in_user` — Get the currently logged-in user's info (no params needed)
 
@@ -77,7 +80,6 @@ User
       "env": {
         "TP_TOKEN": "<your-tp-token>" // Settings -> Authentication and Security -> New Access Token,
         "TP_BASE_URL": "<tp-api-endpoint>",
-        "TP_API_VERSION": "v1",
         "TP_OWNER_ID": "<tp-owner-id>", // your user id
         "TP_PROJECT_ID": "<tp-project-id>",
         "TP_TEAM_ID": "<tp-team-id>"
@@ -102,7 +104,6 @@ User
       "env": {
         "TP_TOKEN": "<your-tp-token>" // Settings -> Authentication and Security -> New Access Token,
         "TP_BASE_URL": "<tp-api-endpoint>",
-        "TP_API_VERSION": "v1",
         "TP_OWNER_ID": "<tp-owner-id>", // your user id
         "TP_PROJECT_ID": "<tp-project-id>",
         "TP_TEAM_ID": "<tp-team-id>"
@@ -115,7 +116,7 @@ User
 
 ### Claude Code
 ```bash
-claude mcp add tarteprocess -s user \
+claude mcp add targetprocess -s user \
   -e TP_TOKEN=<your-tp-token> -e TP_BASE_URL=<tp-api-endpoint> -- npx -y targetprocess-mcp-server
 ```
 

package/build/index.js

@@ -592,9 +592,8 @@ server.registerTool('get_bug_comments', {
 });
 server.registerTool('create_bug_based_on_card', {
     title: 'Create a new bug card based on provided card id',
-    description: `Create a new bug card based on provided card id that summarizes the problem in concise,
-      descriptive manner answering questions What? Where? When?,
-      and content explaining what happened in detail.
+    description: `Create a new bug card based on provided card id that summarizes the problem in concise, descriptive manner answering questions What? Where? When?, and content explaining what happened in detail. 
+      NOTE: this tool requires a user story or bug card as a reference (i.e. card ID).
       CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 
         1) IF you already have user story or bug card content, proceed to step 3 skipping step 2;
         2) ELSE call "get_user_story_content" tool or "get_bug_content" tool to get user story or bug card content;
@@ -650,9 +649,8 @@ server.registerTool('create_bug_based_on_card', {
 });
 server.registerTool('create_bug', {
     title: 'Create a new bug card',
-    description: `Create a new bug card that summarizes the problem in concise,
-      descriptive manner answering questions What? Where? When?,
-      and content explaining what happened in detail.
+    description: `Create a new bug card that summarizes the problem in concise, descriptive manner answering questions "What? Where? When?" and content explaining what happened in detail.
+      NOTE: this tool does not require a user story or bug card referenced.
       CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps:
         1) format the new bug inside html <div> tags with Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior;
         2) add a comment to the newly created bug with its Id and Title`,
@@ -660,11 +658,7 @@ server.registerTool('create_bug', {
         title: z.string()
             .describe('Bug card title that summarizes the problem in concise, descriptive, and actionable manner, enabling a developer to understand the issue without opening the report'),
         bugContent: z.string()
-            .describe(`Bug description content, explain what happened in detail.
-                  Include expected behaviour and what actually occurred.
-                  Be specific and avoid assumptions.
-                  Clearly outline the actions needed to trigger the bug.
-                  Number each step so anyone can follow them easily`),
+            .describe(`Bug description content, explain what happened in detail. Include expected behaviour and what actually occurred. Be specific and avoid assumptions. Clearly outline the actions needed to trigger the bug. Number each step so anyone can follow them easily`),
         origin: z.enum([
             "Production - Customer",
             "Production - Internal",
@@ -858,6 +852,35 @@ server.registerTool('get_feature_user_stories', {
             }],
     };
 });
+server.registerTool('get_projects', {
+    title: 'Get projects',
+    description: 'Get all Targetprocess projects',
+}, async ({}) => {
+    const response = await tp.getProjects();
+    if (!response) {
+        return {
+            content: [{
+                    type: 'text',
+                    text: `Failed to get projects, JSON: ${JSON.stringify(response, null, 2)}`
+                }],
+        };
+    }
+    const items = response.Items || [];
+    if (items.length === 0) {
+        return {
+            content: [{
+                    type: 'text',
+                    text: `No projects found`,
+                }],
+        };
+    }
+    return {
+        content: [{
+                type: 'text',
+                text: JSON.stringify(items.map((p) => ({ id: p.Id, name: p.Name })))
+            }],
+    };
+});
 server.registerTool('get_logged_in_user', {
     title: 'Get logged in user',
     description: 'Get logged in user',

package/build/tp.js

@@ -339,6 +339,12 @@ export class TpClient {
             apiVersion: this.v2
         });
     }
+    async getProjects() {
+        return this.get({
+            pathParam: { "Projects": '' },
+            param: { "format": "json" },
+        });
+    }
     async getContext() {
         return this.get({
             pathParam: { "Context": '' },

package/package.json

@@ -25,7 +25,7 @@
   "engines": {
     "node": ">=20.x"
   },
-  "version": "1.0.21",
+  "version": "1.0.22",
   "description": "MCP server for Tartget Process",
   "main": "build/index.js",
   "keywords": [