Targetprocess MCP Server

Targetprocess MCP Server

An MCP (Model Context Protocol) server that enables AI assistants to interact with the Targetprocess project management platform through structured tools and natural language workflows.

This server exposes powerful capabilities for querying, creating, and managing Targetprocess entities such as user stories, bugs, tasks, and features.

It acts as a bridge between LLM agents and the Targetprocess API, providing:

• Structured tool-based access
• Semantic, natural-language-driven workflows

Features

• Create standalone bugs or bugs linked to a user story/bug card

• Retrieve TP entities: bugs, user stories, features, releases

• LLM-Friendly Tools

  • Designed for Claude MCP AI agents

Use Cases examples:

• "Show me currently active release"
• "write me test cases based on 145322 tp user story"
• "write detailed test cases based on 145642 bug, format them inside html
  element, create a test plan and add test cases to it"
• "add a comment to 145155 card saying 'test'"
• "write test cases based on 145640 feature"
• "create a bug based on 145637 user story where Add Tile flyout (for a Static Tile) not show"
• "search for a card with 'Text Element' title"

Available tools:

Releases

• get_current_releases — List all current releases (no params needed)
• get_release_bugs — Get bugs for a release (name, optional results)
• get_release_features — Get features for a release (name, optional results)
• get_release_user_stories — Get user stories for a release (name, optional results)
• get_release_user_stories_with_description — Same as above but includes full descriptions (name, withDescription)
• get_release_open_bugs — Get only active/open bugs for a release (name, withDescription, optional results)
• get_release_open_user_stories — Get only active/open user stories for a release (name, withDescription, optional results)

Features

• get_feature_content — Get a Targetprocess Feature by ID, including description, state, and progress (id)
• get_feature_comments — Get comments for a feature by its ID (id, optional results)
• get_feature_user_stories — Get all user stories for a feature by its ID (id)
• get_not_covered_user_stories_in_feature — Get user stories in a feature not yet covered by tests, includes covered field based on "Test Automation" custom field (id)

User Stories

• get_user_story_bugs — Get all bugs linked to a user story by its ID (id)

Tasks

• get_in_progress_tasks_and_bugs — Get all Tasks and Bugs currently in "In Progress" state assigned to a given user (userId)
• create_task — Create a new task linked to a user story (title, userStoryId, optional description)
• list_my_user_stories — List User Stories assigned to the current user, optionally filtered by state (optional state, optional take, optional skip)
• list_my_bugs — List Bugs assigned to the current user, optionally filtered by state (optional state, optional take, optional skip)

Cards — Read

• get_card_current_status — Get EntityState, TeamState, and assigned teams for a card (id, optional resourceType: UserStory | Bug | Feature, default: UserStory)
• get_bug_content — Fetch full content of a bug by ID (id)
• get_user_story_content — Fetch full content of a user story by ID (id)
• get_bug_comments — Get comments on a bug (id, optional results)
• get_user_story_comments — Get comments on a user story (id, optional results)
• get_user_story_test_cases — Fetch the linked test plan and all its test cases (with steps) for a user story (resourceId)
• get_card_relations — Get all relations (Dependency, Blocker, Relation, Link, Duplicate) for a card, with direction and the related card (id)
• get_relation_types — List the relation types available in this instance (id + name); use to find the relationType name for create_card_relation (no params)
• search_tp_cards — Search TP cards by keyword or phrase in description (keyword, optional entityType: UserStories | Bugs, default: UserStories)

Cards — Write

• add_comment — Post a comment to any card (id, comment)
• add_comment_with_user — Post a comment to any card and mention a specific user (id, comment, user object from get_users)
• update_bug — Update an existing bug (id, optional title, optional bugContent, optional origin, optional projectId, optional teamId, optional entityStateId)

  Resolve state name → ID via get_bug_workflows before passing entityStateId

• update_user_story — Update an existing user story (id, optional title, optional description, optional projectId, optional teamId, optional entityStateId)

  Resolve state name → ID via get_user_story_workflows before passing entityStateId

• create_card_relation — Create a relation between two cards (masterId, slaveId, optional relationType name, default: "Depends on")

  The Slave depends on the Master — the Master must be done first relationType is matched by name against this instance's types; resolve exact names via get_relation_types (it's resolved to an ID before the API call, since TP rejects relation types passed by name)

• delete_card_relation — Remove a relation by its relation ID (relationId)

  Get the relationId from get_card_relations first — it's the relation's own ID, not a card ID

• update_user_story_state — Update the sub-state (team assignment entity state) for a user story (id, optional entityStateId, optional teamId, optional teamAssignmentId)

  1. Call get_user_story_content first to find the assigned team and teamAssignmentId
  2. Call get_user_story_workflows to resolve the target state name → entityStateId

• set_business_value — Set the Business Value (Priority) on a User Story, Feature, or Epic (id, entityType: UserStories | Features | Epics, priorityId)

  Resolve priorityId via get_priorities first — do not guess priority IDs

• get_priorities — List the Priority options available in this instance, used to resolve a priority name (e.g. "Must Have") to its ID (no params)
• delete_card — Delete a card by ID; works on Bugs, User Stories, Features, and Epics (id, type: Bug | UserStory | Feature | Epic)

  If the type is uncertain, resolve it first via search_tp_cards or by fetching the card

• create_bug — Create a standalone bug (title, bugContent, optional origin, optional projectId, optional teamId, optional entityStateName)

  origin accepted values: Production - Customer, Production - Internal, Pre-Release - Customer, Pre-Release - Internal, Regression - Dev01, Regression - Team Env, Manual QA (default), Developer Raised, Operations entityStateName accepted values: Backlog, In Triage, Ready for Dev, In Dev, Blocked, PR Raised, Ready for Feature PCH, Ready for Feature QA, In Feature QA, Failed Feature QA, Ready for Merge, Ready to Deploy to Dev01, Ready for Dev01 QA, In Dev01 QA, Failed Dev01 QA, Ready to Deploy to prod, Closed

[!NOTE]
projectId and teamId are optional — fall back to TP_PROJECT_ID and TP_TEAM_ID from config

• 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, optional projectId, optional teamId)

[!NOTE]
projectId and teamId are optional — fall back to TP_PROJECT_ID and TP_TEAM_ID from config

• create_user_story — Create a new user story (title, optional description, optional featureId, optional releaseId, optional projectId, optional teamId)

[!NOTE]
projectId and teamId are optional — fall back to TP_PROJECT_ID and TP_TEAM_ID from config

• create_formatted_user_story — Create a new user story with a structured template description in Header → Definitions → Scenarios → Examples Table → Edge Cases → Acceptance Criteria → References → Notes order (title, header object with asA/iWant/soThat, scenarios array with Gherkin steps, acceptanceCriteria array, optional definitions, examplesTable, edgeCases, references, notes, optional featureId, releaseId, projectId, teamId)

[!NOTE]
projectId and teamId are optional — fall back to TP_PROJECT_ID and TP_TEAM_ID from config

• create_epic — Create a new epic (title, optional description, optional releaseId, optional projectId)
• get_epic_content — Get a Targetprocess Epic by ID, including description, state, and progress (id)
• update_epic — Update an epic's title, description, release, or project (id, optional title, optional description, optional releaseId, optional projectId)
• get_epic_features — Get all features belonging to an epic (id)
• create_feature — DEPRECATED, use create_formatted_feature instead for all new features; only call this when you have a fully pre-written HTML description and the user has explicitly opted out of the structured template (title, optional description, optional epicId, optional releaseId, optional projectId, optional teamId)

[!NOTE]
projectId and teamId are optional — fall back to TP_PROJECT_ID and TP_TEAM_ID from config

• create_formatted_feature — Create a new feature with a feature-level TDRE template in Header → Definitions → Scope & Boundaries → Non-Functional Requirements → Cross-Cutting Scenarios → Child Stories → Open Questions/Risks → References → Notes order (title, header object with businessBackground, nonFunctionalRequirements array with area/requirement/status/storyOrOwner, optional definitions, scope, crossCuttingScenarios, childStories, openQuestions, references, notes, optional epicId, releaseId, projectId, teamId)