Targetprocess Integration
STDIOAI assistants interact with Targetprocess data, enabling natural language queries and management.
AI assistants interact with Targetprocess data, enabling natural language queries and management.
The Targetprocess MCP Server enables AI assistants to interact with your Targetprocess data through intelligent semantic operations. Beyond basic data access, it provides workflow-aware tools that understand context, suggest next steps, and adapt to your Targetprocess configuration automatically.
# Basic usage docker run -i --rm \ -e TP_DOMAIN=your-domain.tpondemand.com \ -e TP_USERNAME=your-username \ -e TP_PASSWORD=your-password \ ghcr.io/aaronsb/apptio-target-process-mcp # With semantic operations and strict mode (recommended for MCP clients) docker run -i --rm \ -e TP_DOMAIN=your-domain.tpondemand.com \ -e TP_USERNAME=your-username \ -e TP_PASSWORD=your-password \ -e TP_USER_ROLE=developer \ -e TP_USER_ID=your-user-id \ -e TP_USER_EMAIL=your-email \ -e MCP_STRICT_MODE=true \ ghcr.io/aaronsb/apptio-target-process-mcp
# Basic usage TP_DOMAIN=your-domain.tpondemand.com TP_USERNAME=your-username TP_PASSWORD=your-password \ npx -y https://github.com/aaronsb/apptio-target-process-mcp.git # With semantic operations and strict mode (recommended for MCP clients) TP_DOMAIN=your-domain.tpondemand.com TP_USERNAME=your-username TP_PASSWORD=your-password \ TP_USER_ROLE=developer TP_USER_ID=your-user-id TP_USER_EMAIL=your-email \ MCP_STRICT_MODE=true \ npx -y https://github.com/aaronsb/apptio-target-process-mcp.git
Full installation guide → CLI usage guide →
# Quick setup for development ./scripts/dev-setup.sh # Basic manual setup npm install && npm run build claude mcp add targetprocess node ./build/index.js \ -e TP_DOMAIN=your-domain.tpondemand.com \ -e TP_USERNAME=your-username \ -e TP_PASSWORD=your-password # With semantic operations (recommended) claude mcp add targetprocess node ./build/index.js \ -e TP_DOMAIN=your-domain.tpondemand.com \ -e TP_USERNAME=your-username \ -e TP_PASSWORD=your-password \ -e TP_USER_ROLE=developer \ -e TP_USER_ID=your-user-id \ -e TP_USER_EMAIL=your-email \ -e MCP_STRICT_MODE=true
Claude Code integration guide →
Strict Mode: For MCP clients that require clean JSON-RPC on stdio (like Claude Desktop), enable strict mode to redirect all logging to stderr:
# Environment variable MCP_STRICT_MODE=true # Auto-detection also works for: # - Claude Desktop (stdio transport) # - Non-TTY environments # - When --stdio flag is present
Semantic Operations: Enable intelligent workflow tools with role-based filtering:
TP_USER_ROLE=developer # Options: developer, project-manager, tester TP_USER_ID=your-user-id # For task assignments and time tracking TP_USER_EMAIL=your-email # Identity for semantic operations
Why Enable Semantic Operations?
show_my_tasks
, start_working_on
, complete_task
instead of just raw API calls# Basic usage TP_DOMAIN=your-domain.tpondemand.com TP_USERNAME=your-username TP_PASSWORD=your-password \ npx -y https://github.com/aaronsb/apptio-target-process-mcp.git # With semantic operations (recommended) TP_DOMAIN=your-domain.tpondemand.com TP_USERNAME=your-username TP_PASSWORD=your-password \ TP_USER_ROLE=developer TP_USER_ID=your-user-id TP_USER_EMAIL=your-email \ MCP_STRICT_MODE=true \ npx -y https://github.com/aaronsb/apptio-target-process-mcp.git
# Basic usage docker run -i --rm \ -e TP_DOMAIN=your-domain.tpondemand.com \ -e TP_USERNAME=your-username \ -e TP_PASSWORD=your-password \ ghcr.io/aaronsb/apptio-target-process-mcp # With semantic operations (recommended) docker run -i --rm \ -e TP_DOMAIN=your-domain.tpondemand.com \ -e TP_USERNAME=your-username \ -e TP_PASSWORD=your-password \ -e TP_USER_ROLE=developer \ -e TP_USER_ID=your-user-id \ -e TP_USER_EMAIL=your-email \ -e MCP_STRICT_MODE=true \ ghcr.io/aaronsb/apptio-target-process-mcp
Add to your Claude Desktop configuration file (~/.config/Claude/claude_desktop_config.json
):
Using Docker:
{ "mcpServers": { "targetprocess": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "TP_USERNAME", "-e", "TP_PASSWORD", "-e", "TP_DOMAIN", "-e", "TP_USER_ROLE", "-e", "TP_USER_ID", "-e", "TP_USER_EMAIL", "-e", "MCP_STRICT_MODE", "ghcr.io/aaronsb/apptio-target-process-mcp:latest" ], "env": { "TP_USERNAME": "your-username", "TP_PASSWORD": "your-password", "TP_DOMAIN": "your-domain.tpondemand.com", "TP_USER_ROLE": "developer", "TP_USER_ID": "your-user-id", "TP_USER_EMAIL": "[email protected]", "MCP_STRICT_MODE": "true" }, "disabled": false, "transportType": "stdio" } } }
Using NPX:
{ "mcpServers": { "targetprocess": { "command": "npx", "args": ["-y", "https://github.com/aaronsb/apptio-target-process-mcp.git"], "env": { "TP_USERNAME": "your-username", "TP_PASSWORD": "your-password", "TP_DOMAIN": "your-domain.tpondemand.com", "TP_USER_ROLE": "developer", "TP_USER_ID": "your-user-id", "TP_USER_EMAIL": "[email protected]", "MCP_STRICT_MODE": "true" }, "disabled": false, "transportType": "stdio" } } }
# Quick setup for development ./scripts/dev-setup.sh # Manual setup with Docker claude mcp add targetprocess docker \ -a "run" -a "-i" -a "--rm" \ -a "-e" -a "TP_DOMAIN" \ -a "-e" -a "TP_USERNAME" \ -a "-e" -a "TP_PASSWORD" \ -a "-e" -a "TP_USER_ROLE" \ -a "-e" -a "TP_USER_ID" \ -a "-e" -a "TP_USER_EMAIL" \ -a "-e" -a "MCP_STRICT_MODE" \ -a "ghcr.io/aaronsb/apptio-target-process-mcp:latest" \ -e TP_DOMAIN=your-domain.tpondemand.com \ -e TP_USERNAME=your-username \ -e TP_PASSWORD=your-password \ -e TP_USER_ROLE=developer \ -e TP_USER_ID=your-user-id \ -e TP_USER_EMAIL=your-email \ -e MCP_STRICT_MODE=true # Manual setup with local build npm install && npm run build claude mcp add targetprocess node ./build/index.js \ -e TP_DOMAIN=your-domain.tpondemand.com \ -e TP_USERNAME=your-username \ -e TP_PASSWORD=your-password \ -e TP_USER_ROLE=developer \ -e TP_USER_ID=your-user-id \ -e TP_USER_EMAIL=your-email \ -e MCP_STRICT_MODE=true
# Build and run locally npm install && npm run build node ./build/index.js # For MCP clients requiring JSON config
JSON Configuration for MCP Clients:
{ "mcpServers": { "targetprocess": { "command": "node", "args": ["/path/to/apptio-target-process-mcp/build/index.js"], "env": { "TP_USERNAME": "your-username", "TP_PASSWORD": "your-password", "TP_DOMAIN": "your-domain.tpondemand.com", "TP_USER_ROLE": "developer", "TP_USER_ID": "your-user-id", "TP_USER_EMAIL": "[email protected]", "MCP_STRICT_MODE": "true" }, "disabled": false, "transportType": "stdio" } } }
# Import as a toolkit in watsonx Orchestrate orchestrate toolkits import \ --kind mcp \ --name targetprocess \ --package-root /path/to/apptio-target-process-mcp \ --command '["node", "build/index.js"]' \ --tools "*"
# Examples of what you can ask your AI assistant:
"Show me all open user stories in the mobile app project"
"Create a bug for the authentication failure on the login page"
"What's the status of our Q2 release?"
"Update the priority of story #12345 to high"
"Show me all tasks assigned to Sarah"
"Which team has the most open bugs right now?"
MIT