targetprocess-mcp-server

What it does

This MCP server bridges Claude to Targetprocess, a project management platform. It exposes tools to query and manage work items—user stories, bugs, features, releases, and tasks—and enables operations like creating bugs, adding comments, writing test cases, and updating entity status. The server translates natural language requests into structured API calls, enabling AI-driven project workflows without manual navigation of the Targetprocess UI.

Who it's for

QA engineers, test automation specialists, and project managers who use Targetprocess and want Claude to automate routine work. Common personas: a QA lead asking Claude to generate test cases from a bug description, a PM querying active releases and their open work items, or a developer creating linked bugs within an automated workflow.

Common use cases

• Query current releases and their active bugs or user stories
• Generate test cases from a user story or bug description and create linked test plans
• Search for cards by title or keyword in Targetprocess
• Create bugs linked to existing user stories or features
• Add comments to cards and update their status or content

Setup pitfalls

• Requires Targetprocess API credentials (base URL and authentication token) and environment variables TP_PROJECT_ID and TP_TEAM_ID for most creation operations
• The server reads local configuration and state files (filesystem read access); misconfigured paths will fail silently
• No automated CI suite—the server has no passing tests, so stability depends on manual testing and recent commits