# Yodiz MCP MCP > Yodiz MCP connects your AI agent directly to Yodiz, letting you manage every phase of software development—from tracking initial concepts (epics) through user stories, sprints, and bugs. You ask natural language questions about project status; the MCP finds the answers instantly. ## Overview - **Category:** productivity - **Price:** Free - **Tags:** agile-methodology, scrum, issue-tracking, sprint-planning, backlog-management, release-management ## Description Stop navigating complex boards just to check a simple status update. This MCP connects your AI agent straight into Yodiz, letting you talk directly to your entire agile backlog. Whether you need to see the high-level roadmap (epics), track every bug found in QA, or figure out what tasks belong to a specific sprint, you ask for it conversationally. You’ll get structured data back—no clicking through dozens of filters required. Because project tracking often involves pulling data across many different systems and boards, **Vinkius AI Analytics** tracks every story pulled, showing exactly which items fed into your report, so nothing happens in the dark. This capability makes it a central coordination layer for development teams. You’re not just running reports; you’re coordinating the entire flow of work from concept to completion. It's how product owners keep their roadmaps aligned with reality and how QA engineers can audit technical debt across multiple projects without spending half a day clicking through dashboards. ## Tools ### list_projects Gathers a complete list of every agile project workspace you have access to in Yodiz. ### list_user_stories Retrieves detailed user stories and requirements for any given Yodiz project ID. ### list_sprints Lists all scheduled time-boxed iterations (sprints) for a specific, defined project. ### list_bugs Pulls a list of specific bugs and issues for a single, defined project ID. ### list_epics Retrieves the top-level, large feature groupings (epics) that define the overall scope of a project. ### list_users Lists every registered team member in your workspace, providing IDs needed for assignments. ## Prompt Examples **Prompt:** ``` List all active projects in Yodiz. ``` **Response:** ``` I found 4 active agile projects: 1. 'Cloud Infrastructure v2' (ID: 101), 2. 'Mobile App Redesign' (ID: 102), 3. 'API Gateway' (ID: 103), and 4. 'Internal Tooling' (ID: 104). Which one would you like to review? ``` **Prompt:** ``` Show me the user stories for project ID 102. ``` **Response:** ``` Retrieving stories for project 102... I found 12 items. Top items: 1. 'User Login with SSO' (Status: In Progress), 2. 'Add dark mode support' (Status: Backlog), 3. 'Optimize image loading' (Status: Done). Would you like the full details for any of these? ``` **Prompt:** ``` What sprints are scheduled for project ID 101? ``` **Response:** ``` Project 101 has 3 scheduled iterations: 1. 'Sprint 24 - Networking' (Current), 2. 'Sprint 25 - Security Audit' (Upcoming), and 3. 'Sprint 26 - Scalability' (Future). Would you like to see the start and end dates for these sprints? ``` ## Capabilities ### List all active projects Gathers a master list of every agile workspace you've set up in Yodiz. ### Identify project scope goals Retrieves the high-level strategic features (epics) that define what an entire product line should achieve. ### Track development iterations Lists all planned sprints or timeboxes for a given project, showing when they start and end. ### Review user stories Provides detailed lists of specific requirements (user stories) tied to a numeric project ID. ### Find bugs and issues Collects technical debt items and bugs for any defined project, helping QA track down flaws. ### Locate team members Returns a list of all users in your workspace, giving you IDs needed to assign tasks or mention colleagues. ## Use Cases ### Project discovery and setup You need to know which projects exist before you can track anything. Asking the agent to run `list_projects` immediately gives you all available workspace IDs, letting you pick the right scope for your next task. ### Mid-sprint status check A stakeholder asks about 'Mobile App Redesign'. Instead of opening the project and clicking through menus, your agent runs `list_user_stories` to surface the top 12 items, letting you report progress instantly. ### Bug triage after a release The QA team needs to check technical debt. Running `list_bugs` for 'API Gateway' pulls every known issue into one chat window, saving the manual effort of cross-referencing bug tickets. ### Planning next quarter's work You need to align goals with timelines. Your agent uses `list_epics` and `list_sprints` together to show which strategic features are scheduled for the upcoming quarters. ## Benefits - Stop manual board navigation. Instead of digging through tabs to check a bug, you simply ask the agent for `list_bugs` and get a clean list instantly. - Get immediate strategic context by calling `list_epics`. You see the big picture roadmap without having to sift through thousands of low-level tasks. - Audit team membership and assign work easily. Use `list_users` to pull colleague IDs, making task assignment accurate every time. - Know exactly where development stands by running `list_sprints`, giving you visibility into scheduled iterations for any project. - Keep requirements current with `list_user_stories`. You get a precise list of backlog items tied to a specific numeric ID, eliminating guesswork. ## How It Works The bottom line is you get instant, filtered access to complex project data without ever touching the Yodiz web interface. 1. Connect the Yodiz MCP and provide your API credentials through your preferred AI client. 2. Tell your agent what data you need—for example, 'Show me all bugs for project 102' or 'List all sprints for this quarter.' 3. The agent runs the necessary tool calls and returns a structured list of projects, stories, or issues right in your chat window. ## Frequently Asked Questions **How do I find all projects using list_projects?** The agent runs `list_projects` and gives you a master list of every available workspace ID. You can then pass those IDs to other tools, like listing sprints or users, for targeted reports. **Does list_user_stories need a project ID?** Yes. The `list_user_stories` tool requires the numeric Project ID upfront. You should run `list_projects` first to get that ID before attempting to retrieve stories. **How do I check bugs across multiple projects?** You can't pass a list of IDs at once, but you can chain calls: ask the agent to run `list_projects`, then tell it which three project IDs you want to check. It will call `list_bugs` for each one sequentially. **What is the difference between an epic and a user story?** An epic defines a large, strategic goal (the 'why'), while a user story details a specific feature that achieves part of that goal (the 'what'). You find epics using `list_epics`. **When using list_users, what kind of ID do I get for assigning tasks?** It provides unique numeric IDs for every registered team member. These are the specific identifiers you must pass to other tools if you want your agent to assign a task or mention an individual. **Does list_bugs allow filtering results by bug severity or assignee?** Yes, it accepts optional parameters for advanced filtering. You can narrow down the search using criteria like 'Severity' (e.g., Critical) or filter bugs assigned to a specific user ID. **Can I check future dates when running list_sprints?** The tool retrieves all scheduled iterations, including those that haven't started yet. The output clearly marks the expected start and end dates for upcoming sprints. **If I run list_projects, is there a limit on how many workspaces I can see?** It lists all active projects within your connected Yodiz account scope. If you need to access data from separate organizational instances, those must be configured with additional credentials. **Can I see the list of open bugs for a specific project?** Yes. The `list_bugs` tool allows your AI agent to retrieve all defects and issues reported for a specific project ID, helping you monitor technical debt and priority fixes through chat. **How do I check the requirements in our backlog via conversation?** You can use the `list_user_stories` tool. Provide the unique project ID, and your agent will return a list of backlog items and requirements, ensuring you stay aligned with current development priorities. **Is it possible to see our release timeline and sprints?** Absolutely. Use the `list_sprints` tool to retrieve all iterations configured for a project. Your agent will return the sprint names and IDs, helping you monitor the release cycle and delivery status.