The Targetprocess MCP Server enables interaction with Targetprocess data using natural language and AI assistants for querying, managing, and updating work items. It allows you to:
Search Entities: Find Targetprocess entities (User Stories, Bugs, Tasks, Projects) with advanced filtering and sorting
Get Entity Details: Retrieve specific entity information including related data
Create Entities: Add new work items with customizable fields (name, project, description, assigned user)
Update Entities: Modify existing items by changing properties like status, description, and assignments
Inspect Objects: Explore Targetprocess API structure, object types, and properties
Natural Language Interaction: Process queries through AI assistants like Claude and ChatGPT
Enterprise Features: Handle complex schemas and large datasets with robust error handling
Provides tools for interacting with Targetprocess, a project management and agile planning platform. Enables searching, creating, and updating entities (User Stories, Bugs, Tasks, Features, etc.), querying with complex filters, exploring data models and relationships, and handling authentication and API interactions.
🎯 Targetprocess MCP Server
An MCP (Model Context Protocol) server implementation for Targetprocess project management platform, providing semantic AI-powered operations alongside traditional API access.
Turn your AI assistant into a Targetprocess power user - manage projects, track work, and update tasks through natural conversation.
Installation
Choose your preferred method:
🤖 Claude Desktop
Native integration with Anthropic's Claude Desktop app.
📂 Claude Code
Use with Anthropic's Claude Code IDE (claude.ai/code)
🐳 Docker
Run in an isolated container environment.
Full Docker configuration guide →
📦 NPX
Zero installation required. Perfect for trying out the server.
Full NPX configuration guide →
💻 Local Development
Clone and run locally for development.
Full local development guide →
Related MCP server: Project Handoffs MCP Server
Configuration
API Authentication
Option 1: API Key (Recommended)
Go to Targetprocess → Settings → Access Tokens
Create a new token
Set
TP_API_KEYenvironment variable
Option 2: Basic Auth
Set both:
TP_USERNAME: Your Targetprocess usernameTP_PASSWORD: Your Targetprocess password
⚠️ Security Note: Never commit credentials to version control. Use environment variables or .env files (gitignored).
Available Tools
The server provides these MCP tools to AI assistants:
Tool | Description |
search_entities | Search with powerful filtering, sorting, and includes |
get_entity | Retrieve detailed entity information |
create_entity | Create new work items with validation |
update_entity | Update existing entities |
inspect_object | Explore entity types and properties |
Role-Specific Tools
All tools provide semantic hints and workflow suggestions. When you configure a user role, you get additional specialized tools:
Role | Additional Tools |
|
,
,
,
,
|
| Project oversight and team management tools |
| Test case and bug management tools |
| Backlog and feature prioritization tools |
Environment Variables Reference
Variable | Required | Description |
| Yes | Your Targetprocess domain (e.g., company.tpondemand.com) |
| Yes* | API key for authentication (recommended) |
| Yes* | Username for basic authentication |
| Yes* | Password for basic authentication |
| No | Enable role-specific tools:
,
,
,
|
| No | Your Targetprocess user ID (for assignments) |
| No | Your email (for identification) |
| No | Set to
for MCP clients requiring clean JSON-RPC |
*Either API key or username/password required
For detailed configuration examples, see the guides above.
IBM watsonx Orchestrate Integration
What can I do with it?
Documentation
Getting Started - First steps and basic usage
Core Concepts - Understanding the key components
Tools Reference - Detailed API documentation
Use Cases - Common workflows and examples
AI Integration - Setting up with Claude, ChatGPT, etc.
Architecture - System design and implementation
Development - Contributing and extending
Features
Role-Specific Tools (Developer Role)
When configured with TP_USER_ROLE=developer, these additional tools become available:
show_my_tasks: View assigned tasks with smart filtering and priority analysis
start_working_on: Begin work on tasks with automatic state transitions
complete_task: Mark tasks complete with integrated time logging and comments
show_my_bugs: Analyze assigned bugs with dynamic severity categorization
log_time: Record time with intelligent entity type discovery and validation
add_comment: Add contextual comments with workflow-aware follow-up suggestions
Note: All tools (both core and role-specific) provide semantic hints and workflow suggestions.
Core API Tools
Entity Management: Create, read, update, and search Targetprocess entities
Complex Queries: Filter items by custom fields, status, relationships, and more
Data Discovery: Explore entity types, properties, and relationships
Rich Includes: Retrieve related data in a single request
Enterprise Features
Role-Based Access: Tools filtered by personality configuration (developer, PM, tester)
Dynamic Discovery: Adapts to custom Targetprocess configurations automatically
Error Resilience: Transforms API failures into actionable guidance
Documentation Access: Built-in access to Targetprocess documentation
LLM Integration: Works with Claude, ChatGPT, and other AI assistants
License
MIT