# Targetprocess MCP > Targetprocess MCP connects your AI client to Apptio Targetprocess for enterprise Agile planning. It lets you query detailed product backlogs, track user stories and active bugs, and map out global project features directly from the terminal. Stop switching between web dashboards; get constant programmatic awareness of your organization's roadmap execution. ## Overview - **Category:** developer-tools - **Price:** Free - **Tags:** agile-planning, scrum-master, portfolio-management, bug-tracking, sprint-planning, visual-management ## Description Running an agile portfolio is complex enough without constantly fighting clunky management panels. This MCP gives your AI client direct access to Apptio Targetprocess data, letting you treat your entire product backlog like a text document. You can ask your agent to pull together the current sprint schedule and cross-reference it against high-priority bugs. Need to map out what features are currently being developed? It's there. This integration lets you bypass the graphical interface friction that slows down deep work, providing programmatic awareness of everything from global project scopes to individual user story requirements. Because this MCP lives in Vinkius, you connect once and gain access to all your specialized tools across multiple systems. ## Tools ### list_bugs Reads a list of currently reported technical defects or anomalies in the system. ### list_features Generates a structured list of high-level product capabilities and features. ### list_iterations Retrieves active time containers, showing which sprints or cycles are currently running. ### list_projects Lists every defined project within the Targetprocess account. ### list_user_stories Fetches detailed records of specific user stories, capturing requirement specifications. ### list_account_users Provides a complete list of all registered users in the Targetprocess account. ## Prompt Examples **Prompt:** ``` Retrieve the current active Sprint iterations and pull the details of the top 3 unassigned bugs logged under our primary development project. ``` **Response:** ``` Gathering structural records ('list_iterations')... Evaluating active Sprint: 'Iteration Q4-B'. Now querying current technical debts via 'list_bugs'... **Found Top Defects**: - Bug-145: 'Memory leak in auth parser' (Critical) - Bug-199: 'Missing CSS button radius' (Medium) - Bug-231: 'Gateway timeout during 2FA' (High) ``` **Prompt:** ``` Extract the details for user story #4552 in the current sprint. ``` **Response:** ``` Interrogating agile entities ('get_entity_details')... User Story #4552: 'Implement SSO Auth' - State: In Progress - Assigned to: Alice B. - Story Points: 5 - Iteration: Sprint 14 ``` **Prompt:** ``` List all high priority bugs that are currently 'Open'. ``` **Response:** ``` Querying Targetprocess data ('search_entities')... I found 2 'Open' bugs tagged with High Priority: 1. Bug #5120: 'Payment gateway timeout in production' 2. Bug #5125: 'Null pointer exception on invoice generation' ``` ## Capabilities ### Audit current technical debt List reported bugs and defects against active projects without leaving your coding environment. ### Map project scopes and features Get structured lists of all defined global products, capabilities, and parent projects in the system. ### Track sprint timing and commitments Query active sprints and time-bound iterations to see what the team is currently focused on. ### Read requirement specifications Pull detailed product backlogs by listing specific user stories assigned to a project. ### Identify all system users Retrieve a list of every registered user within the Targetprocess account for auditing purposes. ## Use Cases ### Diagnosing sprint blockers A team lead notices delays during a review. Instead of asking three people, they prompt their agent: 'What are the active issues tracked in our main project and what is the current iteration?' The MCP runs list_bugs and list_iterations together, immediately highlighting the confluence of technical debt and limited time. ### Validating feature scope An owner needs to prove that a new capability (feature) supports three specific user stories. They prompt their agent to run list_features first, then use list_user_stories to confirm the exact requirements against the global product map. ### Pre-release compliance audit A release manager needs a snapshot of all technical assets involved in the deployment. They ask their agent to list_projects, then immediately run list_account_users and list_features to ensure every user has access to the necessary components. ### Quickly getting context on new hires A manager needs to understand who is working in a specific product line. They simply ask their agent to run list_account_users, receiving a structured roster without logging into any user management portal. ## Benefits - You get instant visibility into technical debt. Instead of manually navigating a bug dashboard, you can query list_bugs to find all high-priority defects right in your prompt. - Stop guessing about team focus. By calling list_iterations, your agent tells you exactly which sprint the development cycle is currently operating within. - Mapping requirements becomes simple. You don't need to click through menus; asking for list_user_stories pulls detailed specs instantly, validating needs against the actual product backlog. - Understand the big picture scope by calling list_features and list_projects. This lets you see the entire global hierarchy of products without leaving your terminal. - Streamline audits with list_account_users. You can pull a roster of every registered user directly into your workflow for compliance checks. ## How It Works The bottom line is you use natural language to run complex portfolio reports that usually require five different web clicks and three hours of context switching. 1. First, you connect your AI client to this MCP via Vinkius and provide your organizational host ID and access token. 2. Next, you prompt your agent with a complex request, such as asking for the top three unassigned user stories while also listing all open bugs. 3. Finally, your agent executes the necessary functions in sequence, returning structured data that pinpoints exactly what's happening across your entire product roadmap. ## Frequently Asked Questions **How do I use Targetprocess MCP to find out what bugs are open?** You call the list_bugs tool. This function queries and provides you with a structured array listing all currently reported defects, allowing you to assess technical debt immediately. **Can Targetprocess MCP show me which sprint we're in?** Yes, use the list_iterations tool. It fetches time-bound records showing the active sprints and development cycles for your team. **Does Targetprocess MCP help with project mapping?** Absolutely. You can run list_projects to see all defined projects, and then use list_features to understand the high-level capabilities associated with those projects. **How do I find out who works in my Targetprocess account?** Run the list_account_users tool. This provides a full roster of every registered user within your organization's instance.