All servers / Project management / Targetprocess MCP server
Targetprocess MCP server
MCP server for Tartget Process
Tested by ConnectATDScore 84 out of 100. Tested 2026-11-19 on package version 2.8.2. Package: targetprocess-mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 18 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (11.1 seconds including download)
- Tools offered: 76
- Last published: 2026-11-17
- Weekly downloads (npm): 762
- License: ISC · Direct dependencies: 10
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
get_user_story_content1 of 1 parameter describedGet tp card (user story) content by specified id, e.g. 145789
get_current_releasesno parametersGet current releases
get_release_user_stories2 of 2 parameters describedGet release user stories
get_release_bugs3 of 3 parameters describedGet release bugs
get_release_features2 of 2 parameters describedGet release features
get_release_user_stories_with_description2 of 2 parameters describedGet release user stories with description in the response. Note: this is slower than "get_release_user_stories_names" tool, but if user wants to get descriptions, then this tool is the way to go.
get_release_open_bugs3 of 3 parameters describedGet release active bugs (bugs that are not closed, done, passed, ready to deploy)
get_release_open_user_stories3 of 3 parameters describedGet release active user stories (user stories that are not closed, done, passed, ready to deploy)
search_tp_cards2 of 2 parameters describedSearches TP cards (UserStories or Bugs) by keyword or phrase or partial keyphrase in Card Description e.g. "Text Element", "Font field" NOTE: after results are returned, try analyze and filter results by most relevant to what user is looking for in the description text FALLBACK: if no results are found, try spliting phrase by spaces and searching for each word and with "Generals" entity type
get_bug_content1 of 1 parameter describedGet tp card (bug) content by specified id, e.g. 145789
get_user_by_id1 of 1 parameter describedGet user by id
get_usersno parametersGet all users
add_comment_with_user3 of 3 parameters describedAdds provided content as a comment to the specified tp card by id, e.g. 145789 and mentions the user in the comment CRITICAL WORKFLOW: 1) call 'get_users' to get list of available users 2) find the user by email, first name, or last name in the users list
add_comment2 of 2 parameters describedAdds provided content as a comment to the specified tp card by id, e.g. 145789
add_attachment4 of 4 parameters describedUpload a file (e.g. a screenshot or mockup) as an attachment on a Targetprocess card (bug, user story, feature, etc.) by its ID. filePath is read from THIS MCP SERVER'S OWN filesystem, not the calling assistant's — it only works for a file already on this machine. For an image attached/pasted/uploaded directly in the chat, read its bytes yourself and pass fileContent (base64) + fileName instead; passing that attachment's sandboxed path as filePath will fail with "file not found".
get_user_story_comments2 of 2 parameters describedGet comments for a TP user story by its ID
get_bug_comments2 of 2 parameters describedGet comments for a TP bug by its ID
create_bug_based_on_card6 of 7 parameters describedCreate 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, bug, or feature 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, bug, or feature card content, proceed to step 3 skipping step 2; 2) ELSE call "get_user_story_content" tool, "get_bug_content" tool, or fetch the feature to get card content; 3) format the new bug inside html <div> tags with Environment (describes where bug was found, dev, feature, review or uat Environment), Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior and Attachments sections (note: section titles should be wrapped in <h3> tags, e.g. <h3>Issue Description</h3>); 4) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 5) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 6) IF the user specified a release by name (not ID), call "get_current_releases" to find the matching release and use its ID as releaseId; 7) add a comment to the card with created bug Id and its Title
update_bug10 of 10 parameters describedUpdate a bug card with data proded from user input. NOTE: pass only the fields that user wants to update. CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 2) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 3) IF the user specified a state by name (not ID), call "get_bug_workflows" to find the matching state and use its ID as entityStateId; 4) IF the user specified a sprint/iteration by name, call "get_team_iterations" to find the matching iteration and use its ID as teamIterationId; 5) IF the user specified a release by name (not ID), call "get_current_releases" to find the matching release and use its ID as releaseId;
update_user_story_state4 of 4 parameters describedUpdate a user story card sub state with data provided from user input. CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) call "get_user_story_content" to find the matching team, assigned (responsible) team and their IDs 1) call "get_user_story_workflows" to find matching state and use its ID in entityStateId
set_business_value3 of 3 parameters describedSet the Business Value (Priority) on a Targetprocess User Story, Feature, or Epic. Business Value in the TP UI maps to the Priority field in the API. CRITICAL WORKFLOW: Call "get_priorities" first to retrieve the list of valid priority IDs and their names for this instance before calling this tool — do not guess priority IDs.
get_prioritiesno parametersReturns the list of Priority options available in this Targetprocess instance. Use this before calling "set_business_value" to resolve a priority name (e.g. "Must Have", "Normal", "10") to its ID.
update_user_story9 of 9 parameters describedUpdate a user story card with data provided from user input. NOTE: pass only the fields that user wants to update. CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 2) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 3) IF the user specified a state by name (not ID), call "get_user_story_workflows" to find the matching state and use its ID as entityStateId; 4) IF the user specified a sprint/iteration by name, call "get_team_iterations" to find the matching iteration and use its ID as teamIterationId;
create_bug9 of 9 parameters describedCreate 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 reference. CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) format the new bug inside html <div> tags with Environment(describes where bug was found, dev, feature, review or uat Environment), Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior and Attachments sections (note: section titles should be wrapped in <h3> tags, e.g. <h3>Issue Description</h3>, step to reproduce should be wrapped in <ol>); 2) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 3) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 4) IF the user specified a sprint/iteration by name, call "get_team_iterations" to find the matching iteration and use its ID as teamIterationId; 5) IF the user specified a release by name (not ID), call "get_current_releases" to find the matching release and use its ID as releaseId;
create_user_story8 of 8 parameters describedCreate a new user story in Targetprocess. CRITICAL WORKFLOW: Before calling this tool, IF the user specified a sprint/iteration by name, call "get_team_iterations" to find the matching iteration and use its ID as teamIterationId.
create_formatted_user_story15 of 15 parameters describedCreate a new user story in Targetprocess with a structured, template-driven description, assembled from discrete sections and stored as HTML. Fill in each field to this quality bar: 1) Header — "asA" and "iWant" must be filled in, and "soThat" MUST be a real business outcome, not a restatement of "iWant"; 2) Definitions — check for jargon, feature flags, module names, and acronyms; if none apply, OMIT the "definitions" field entirely (do not send an empty section); 3) Scenarios (write these BEFORE acceptanceCriteria) — at least one Gherkin scenario per distinct behavior; each scenario has exactly ONE "Then" outcome (split it into two scenarios if it needs two); avoid vague verbs like "system validates input" — spell out exactly what "validates" means in the "Then" step; 4) Examples Table — if any behavior is described as "supports various formats/roles/states", convert it into a Scenario Outline (one of the "scenarios" entries) plus a matching "examplesTable" with real values; if no parameterized behavior exists, OMIT "examplesTable"; 5) Edge Cases — MANDATORY (include at least one error-state scenario and one boundary-condition scenario in "edgeCases") if the story touches validation/input handling, permissions/roles, or external data/integrations; otherwise OMIT "edgeCases"; 6) Acceptance Criteria — every bullet MUST be traceable to a specific scenario or edge case above; if a bullet isn't backed by a scenario, it isn't a criterion yet — put it in "notes" as a flagged gap instead; 7) References — put mockup/spec links here, not inline in prose; 8) Notes — capture open questions or known constraints here; don't let them hide inside acceptanceCriteria; CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) IF the user specified a feature by name (not ID), call "get_feature_user_stories" or "search_tp_cards" to resolve the feature ID; 2) IF the user specified a release by name (not ID), call "get_current_releases" to resolve the release ID; 3) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 4) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 5) IF the user specified a sprint/iteration by name, call "get_team_iterations" to find the matching iteration and use its ID as teamIterationId;
create_formatted_feature14 of 14 parameters describedCreate a new Feature in Targetprocess with a structured, template-driven description (feature-level TDRE), assembled from discrete sections and stored as HTML. Features sit above user stories — this template isn't about writing Gherkin for individual behaviors (that belongs on child stories); it's about tracking cross-cutting constraints, risks, and open questions to a testable/decided state before they get lost across many separate stories. Fill in each field to this quality bar: 1) Header — "businessBackground" is a 1-2 sentence value statement: who benefits and why; 2) Definitions — cross-cutting terms used across multiple child stories, so they aren't redefined at every story level; if none apply, OMIT "definitions" entirely (do not send an empty section); 3) Scope & Boundaries — what this feature explicitly includes/excludes, to stop child stories drifting into adjacent features; omit if genuinely trivial; 4) Non-Functional Requirements ("nonFunctionalRequirements") — this is the core of the template and doubles as ISO 27001:2022 audit evidence that NFRs (including information security, per Annex A Control 5.8) are considered at design time, not bolted on after. EVERY feature MUST include these four fixed rows, worded exactly as below (do not reword the questions — consistency in the questions is what makes them auditable), each answered SPECIFICALLY for this feature in "storyOrOwner" — a real, checkable answer (e.g. which systems/data/roles are involved), never a generic "considered" placeholder: - area "System performance" / requirement "What does this feature add or change in terms of load, queries, polling, rendering etc., and what's the expected impact, if any?"; - area "Information security (ISO 27001:2022 Annex A 5.8)" / requirement "What personal or sensitive data does this feature touch, and what protects its privacy, confidentiality, integrity and availability?"; - area "Quality control" / requirement "How will this feature's behaviour and failures be measured or tested, and what happens when it fails?"; - area "Service logging" / requirement "What events or states should be logged so product support can diagnose an issue without reproducing it manually?"; For each row, set status to "Covered" (storyOrOwner holds the specific answer, or the child story/scenario that proves it), "Gap" (no answer/story yet — storyOrOwner names who should follow up), or "Decision needed" (genuinely open, not answerable yet). If any of the four is unclear, follow-up owner in rather than guessing — he's the named escalation contact, not a mandatory sign-off gate. Additional NFR categories beyond these four (Compliance, Billing, Operational, etc.) can still be added as extra rows when relevant, using the same Covered/Gap/Decision-needed treatment; 5) Cross-Cutting Scenarios — ONLY for behavior spanning multiple child stories that wouldn't naturally sit in any one of them (e.g. tenant isolation across all stories); do not duplicate per-story Gherkin here; omit if none apply; 6) Child Stories ("childStories") — pull this from "get_feature_user_stories" / "get_not_covered_user_stories_in_feature" rather than retyping it; keep it as a live pointer, not a duplicate spec; normally empty when first creating the feature; 7) Open Questions / Risks ("openQuestions") — anything raised at feature conception that hasn't been resolved into either a Covered NFR row or a child story; this is the section most likely to get silently dropped — treat it as the running "not done yet" list until each line is promoted to a Covered NFR row; 8) References — mockup/spec links here, not inline in prose; 9) Notes — anything else that helps understand context but doesn't fit other sections; CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) IF the user specified an epic by name (not ID),…
create_feature6 of 6 parameters describedDEPRECATED — use "create_formatted_feature" instead for all new features. Only call this tool when you have a fully pre-written HTML description and the user has explicitly opted out of the structured template.
update_feature10 of 10 parameters describedUpdate a feature card with data provided from user input. NOTE: pass only the fields that user wants to update. CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) IF the user specified an epic by name (not ID), resolve the epic ID first; 2) IF the user specified a release by name (not ID), call "get_current_releases" to resolve the release ID; 3) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 4) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 5) IF the user specified a sprint/iteration by name, call "get_team_iterations" to find the matching iteration and use its ID as teamIterationId;
create_epic4 of 4 parameters describedCreate a new Epic in Targetprocess.
get_epic_content1 of 1 parameter describedGet a Targetprocess Epic by ID, including its description, state, and progress.
update_epic5 of 5 parameters describedUpdate a Targetprocess Epic. Pass only the fields to change.
get_epic_features1 of 1 parameter describedGet all Features belonging to a Targetprocess Epic.
create_test_plan4 of 4 parameters describedCreate a new test plan linked to a UserStory, Bug, or Feature. Name and Project are required by the API; Description, StartDate, and EndDate are optional.
get_not_covered_user_stories_in_feature1 of 1 parameter describedGet user stories for a TP feature by its ID that are not covered by any tests
get_feature_user_stories1 of 1 parameter describedGet user stories for a TP feature by its ID
get_feature_content1 of 1 parameter describedGet a Targetprocess Feature by ID, including description, state, and progress
get_feature_comments2 of 2 parameters describedGet comments for a TP feature by its ID
get_assignment_rolesno parametersReturns all available assignment roles (e.g. Business Analyst, Developer) with their IDs.
assign_role3 of 3 parameters describedAssigns a user to a specific role on a single TP card (User Story, Bug, etc.).
assign_role_to_feature3 of 3 parameters describedAssigns a user to a specific role on every user story within a given feature.
get_user_story_bugs1 of 1 parameter describedGet bugs linked to a TP user story by its ID
get_projectsno parametersGet all Targetprocess projects
get_teams_and_team_assignmentsno parametersGet all Targetprocess teams and team assignments
get_teamsno parametersGet all Targetprocess teams
get_team_iterations1 of 1 parameter describedGet Targetprocess team iterations (sprints), optionally filtered by team. Use this to resolve a sprint/iteration name to an ID before calling create_user_story, create_bug, update_user_story, or update_bug with teamIterationId. CRITICAL WORKFLOW: IF the user specified a team by name (not ID), call "get_teams" first to find the matching team and use its ID as teamId.
get_logged_in_userno parametersGet logged in user
get_user_story_test_cases1 of 1 parameter describedFetches a TP UserStory Linked Test Plan and fetches its Test Cases by provided card ID.
write_test_cases2 of 2 parameters describedFetches a TP card (UserStory, Bug, or Feature) content by ID. CRITICAL WORKFLOW — after receiving the card content, you MUST: 1) Thoroughly analyze the card name and description to understand the feature or issue being tested 2) Write detailed test cases covering: happy path, edge cases, boundary conditions, and error scenarios 3) For each test case produce: - name: concise action-oriented title - description: HTML <div> with Preconditions and Test Type sections only (no steps here) - steps: ordered array of { description: "<step action>", result: "<expected result>" } 4) Call "create_test_plan" tool passing: resourceId (the card id), resourceType, testPlanTitle (use the card name/title), NOTE: IF test plan already exists - skip this step and proceed to step 5. 5) Call "add_test_cases_to_test_plan" tool passing: testPlanId (the test plan id), and the testCases array with name, description, and steps
add_test_cases_to_test_plan2 of 2 parameters describedAdds generated test cases to a test plan linked to a TP card (UserStory, Bug, or Feature).
get_process_workflows1 of 1 parameter describedGet all Targetprocess process workflows
get_processesno parametersGet all Targetprocess processes
get_bug_workflowsno parametersGet all Targetprocess bug workflows
get_user_story_workflowsno parametersGet all Targetprocess user story workflows, with sub-states
get_card_current_status2 of 2 parameters describedGet the EntityState, TeamState, and assigned teams for a TP card (UserStory, Bug, or Feature) by ID
get_card_relations1 of 1 parameter describedGet all relations (Dependency, Blocker, Relation, Link, Duplicate) for a TP card (UserStory, Bug, Feature, etc.) by its ID. Each relation shows the related card and the direction: - "outbound" — this card is the Master (e.g. for Dependency, the related card depends on this card) - "inbound" — this card is the Slave (e.g. for Dependency, this card depends on the related card)
get_relation_typesno parametersGet all relation types available in this Targetprocess instance (id + name). Use this to find the correct relationType name for "create_card_relation".
create_card_relation3 of 3 parameters describedCreate a relation between two TP cards (UserStory, Bug, Feature, etc.). The Master is the source of the relation and the Slave is the target — e.g. for a "Depends on" relation, the Slave depends on the Master (Master must be done first). NOTE: relationType is matched by name against this instance's relation types. If unsure of the exact name, call "get_relation_types" first. The handler resolves the name to its ID before creating the relation.
delete_card_relation1 of 1 parameter describedDelete (remove) a relation between two TP cards by the relation's own ID — not the card IDs. To find the relationId, call "get_card_relations" for one of the cards; each entry includes a "relationId" field.
delete_card2 of 2 parameters describedDelete (remove) a Targetprocess card by its ID. Works on Bugs, User Stories, Features, and Epics. IF the type is uncertain, resolve it first via "search_tp_cards" or by fetching the card.
get_in_progress_tasks_and_bugs1 of 1 parameter describedGet all Tasks and Bugs currently in "In Progress" state assigned to a given user ID
create_task3 of 3 parameters describedCreate a new task linked to a user story.
get_commit_message2 of 2 parameters describedReturns the formatted commit message string for a given task or bug ID. Formats: - Task on a user story: "F#<featureId> US#<userStoryId> T#<taskId> <title>" - Bug on a user story: "F#<featureId> US#<userStoryId> B#<bugId> <title>" - Standalone bug (no user story): "B#<bugId> <title>"
list_my_user_stories3 of 3 parameters describedList User Stories assigned to me. Use this to get an overview of current work. Optionally filter by state.
list_my_bugs3 of 3 parameters describedList Bugs assigned to me. Optionally filter by state.
log_time5 of 5 parameters describedLog time spent working on a Task, User Story, or Bug. Call this after completing a task or at the end of a work session.
get_my_time_logs1 of 1 parameter describedGet recent time log entries submitted by me.
get_versionno parametersReturns the current version of the MCP server from package.json.
get_test_plan_by_id1 of 1 parameter describedGet a Targetprocess Test Plan by its ID, including name, plain-text description, state, and linked card.
get_test_plan_test_cases_by_id1 of 1 parameter describedGet test cases belonging to a Targetprocess Test Plan by plan ID, including cases in nested child test plans/containers. Returns id, name, plain-text description, and containing test plan metadata (no steps).
get_test_plan_test_cases_with_steps_by_id1 of 1 parameter describedGet test cases belonging to a Targetprocess Test Plan by plan ID, including nested child test plans/containers and each test case steps.
get_test_case_by_id1 of 1 parameter describedGet a single Targetprocess Test Case by its ID, including plain-text description and its steps.
update_test_case_by_id3 of 3 parameters describedUpdate a Targetprocess Test Case by its ID. Supports name and description only.
add_test_case_step_by_id3 of 3 parameters describedAdd a new step to a Targetprocess Test Case. Despite tool name consistency, this takes testCaseId, not a step ID.
update_test_case_step_by_id3 of 3 parameters describedUpdate a Targetprocess Test Step by its ID. Supports description and result only.
delete_test_case_step_by_id1 of 1 parameter describedDelete a Targetprocess Test Step by its ID.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.