Yodiz MCP. Query Stories, Sprints, and Bugs via Chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Yodiz manages your entire agile development lifecycle—from high-level epics down to specific bugs and user stories. It connects any AI client directly to your project data, letting you track requirements, monitor sprints, and manage team members without opening the Yodiz UI.
Use it to query projects, check bug status, or list users via simple chat commands.
What your AI agents can do
List bugs
Retrieves a list of bugs and technical debt items for a specific project ID.
List epics
Lists all epics (high-level features) associated with a given project.
List projects
Returns a list of every agile project available in the Yodiz account, along with their IDs.
Runs list_projects to retrieve names and unique identifiers for every agile project in the Yodiz account.
Uses list_bugs to pull all listed issues or technical debt items associated with a single, specified project ID.
Executes list_user_stories, requiring a numeric Project ID, to retrieve every story item currently in that project's queue.
Runs list_sprints using a Project ID to list all planned iterations (sprints) and their associated timelines.
Calls list_epics for a project, showing the high-level features that guide the product's overall direction.
Runs list_users to provide a comprehensive list of all users in your workspace, including their unique IDs for task assignment.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Yodiz MCP Server: 6 Tools for Agile Project Management
Use these six dedicated tools to pull structured data on your entire agile workflow—from high-level epics down to individual bugs and team members.
019d7626list bugs
Retrieves a list of bugs and technical debt items for a specific project ID.
019d7626list epics
Lists all epics (high-level features) associated with a given project.
019d7625list projects
Returns a list of every agile project available in the Yodiz account, along with their IDs.
019d7625list sprints
Outputs all scheduled sprints (iterations) for a specific project ID, including timeline details.
019d7625list user stories
Provides a list of user stories within a specified Yodiz project, requiring the numeric Project ID.
019d7626list users
Returns a complete directory of all registered users in your workspace for task assignment or reference.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Yodiz, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Yodiz lets you run your AI client straight against your project data. Ya don't gotta open up those messy boards or wrestle with the Yodiz UI just to check what's going on. This server exposes tools that map directly to every core piece of an agile backlog: projects, users, bugs, epics, stories, and sprints.
You can use your agent to pull raw, structured information—you get clean data back every single time.
To start, you gotta know what's available. Run list_projects and it spits out a list of every agile project in the Yodiz account, giving you the names and unique IDs for each one. Need to find team members? Running list_users gives you the full directory of every registered user in your workspace, complete with their specific IDs for assignment.
Once you've got a Project ID, you can dig deep into the plan. You'll see all the high-level features—the epics that guide the product's overall direction—by calling list_epics. For detailed requirements, use list_user_stories to grab every story item in that project's queue. If you need to know when things are due, run list_sprints; this outputs all planned iterations and their associated timeline details.
You can also get a full picture of the development scope by running list_projects to list all projects.
When it comes to quality control, you've got two tools. First, use list_bugs to pull every listed issue or technical debt item for a specific project ID. Second, if you want to know exactly what needs doing in the backlog, running list_user_stories gives you that full list of requirements.
In short, your agent can run through everything: it'll grab all projects via list_projects, map out the roadmap with list_epics, check the user stories using list_user_stories, get sprint dates with list_sprints, pull bug reports with list_bugs, and give you a directory of people with list_users.
How Yodiz MCP Works
- 1 Subscribe to the Yodiz server and input your API credentials (API Key, Email, Password).
- 2 Ask your AI client a direct question, like 'List all bugs for Project 102.'
- 3 The agent invokes the correct tool (
list_bugs), gets the structured data from Yodiz, and reports it back to you.
The bottom line is that your agent talks to the Yodiz API directly. You bypass the UI entirely by asking for specific lists of data like stories or sprints.
Who Is Yodiz MCP For?
Scrum Masters, Product Owners, and QA Engineers are the primary users here. They hate manually clicking through dashboards just to check a sprint status or find an old bug report. This server lets them query structured data—like finding all user stories for Epic X—in plain chat.
Uses list_epics and list_user_stories to quickly pull strategic details, confirming if the current backlog aligns with business goals without opening the project board.
Runs checks like list_sprints and list_bugs to audit sprint health, verifying that all technical debt items are accounted for in the current iteration plan.
Uses list_bugs across multiple projects to aggregate defect reports, ensuring no critical issues slip through manual testing cycles.
What Changes When You Connect
- Bypass manual navigation. Instead of clicking through project boards to find a bug's status, you simply ask your agent to run
list_bugsand get the report instantly. It saves minutes every hour. - See the full roadmap at once. Use
list_epicsto pull all high-level goals for a product line. You don't have to jump between tabs just to align stakeholders on strategy. - Audit team members easily. Running
list_usersgives you every colleague ID in one shot. Assigning tasks or checking permissions becomes instant, without consulting the internal directory. - Monitor release timelines fast. Your agent handles the complexity of
list_sprints, giving you all upcoming iterations and their start/end dates for a project ID instantly. - Get granular requirements data. With
list_user_storiesand knowing the Project ID, you get every single backlog item needed to scope out development work. No guessing which stories are active. - Keep track of everything. By combining calls—like first using
list_projectsthen feeding those IDs intolist_bugs—you build a comprehensive view without leaving your chat window.
Real-World Use Cases
Tracking Scope Creep for Product Owners
The PO needs to know if the latest feature request was already planned. Instead of digging through old Jira tickets, they ask their agent: 'Show me all epics related to payment processing.' The agent runs list_epics and surfaces the scope immediately, confirming alignment.
Pre-Release QA Bug Sweep
QA needs a full bug count for Project X before launch. They ask: 'What are all open bugs in Project 105?' The agent calls list_bugs(project=105) and returns the complete, current list of technical debt items, preventing missed issues.
Checking Team Availability for Sprints
A Scrum Master needs to confirm who is available next month. They first use list_users to get all team member IDs, then they check the schedule using list_sprints for Project Alpha, ensuring enough resources are allocated.
Comparing Backlog vs. Plan
A development lead wants to compare planned work versus actual backlog items. They run list_user_stories and then cross-reference the results with list_sprints. This immediate comparison helps them identify stories that are falling out of sync with the current iteration.
The Tradeoffs
Trying to list everything in one go
Manually running a search query for 'everything related to Project Alpha' and getting 10 pages of mixed, unsorted data across stories, bugs, and epics.
→
Don't try to do it all at once. First, use list_projects to confirm the ID. Then, break down your request: 'First, run list_epics. Second, for those results, run list_user_stories.' Step-by-step queries are cleaner.
Confusing Epics and Stories
Asking the agent to list all 'large features' and getting a vague response that mixes high-level goals with individual tasks.
→
Be specific. Use list_epics when you mean the macro goal (the whole area). Only use list_user_stories when you need discrete, actionable requirements for development.
Ignoring Project IDs
Asking 'Show me bugs' without specifying which project. The agent either fails or returns a massive list that includes unrelated data from other projects.
→
Always get the ID first. Start with list_projects to find the target ID, and then pass it directly into tools like list_bugs (e.g., 'List bugs for Project 103').
When It Fits, When It Doesn't
Use this server if your primary job is retrieving structured project data from Yodiz. You need to know what the backlog looks like, when it's scheduled, and who owns the task, all without clicking through UI tabs.
Don't use this if you need to update a field (e.g., change a status or assign a user) or run complex reports that require data manipulation outside of simple listing. If you just need to know 'What is the current bug count?'—use list_bugs. If you only care about team structure, stick to list_users. This server excels at read-only discovery and aggregation.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Yodiz. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 6 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Finding project scope shouldn't require 3 clicks and a deep dive into six different tabs.
Today, figuring out if an Epic is still relevant means jumping from the main dashboard to the 'Epics' tab. Then you click into that Epic, navigate to the related 'Stories,' and finally check the status board for any associated bugs. It’s a tedious copy-paste dance just to confirm scope.
With this MCP server, your agent pulls the data directly from Yodiz. You ask: 'What are all the active epics for Project 102?' The response is immediate and structured, giving you the full picture in one shot—no tabs, no clicks.
Using `list_bugs` lets QA Engineers aggregate defect reports across multiple projects.
Before this, tracking technical debt meant manually running separate bug reports for every project ID and then compiling them into a master spreadsheet. If you missed one project, the report was incomplete.
Now, you use `list_bugs` sequentially or in a workflow to grab defect lists from several different projects. You get a clean, aggregated list of issues that instantly tells you where your code quality gaps are.
Common Questions About Yodiz MCP
How do I find the ID needed for `list_user_stories`? +
First, run list_projects. This tool returns all project names and their required numeric IDs. You must use one of those returned Project IDs when calling list_user_stories.
Can I check for bugs across multiple projects using `list_bugs`? +
The current tool requires a single Project ID. To cover multiple projects, you must first use list_projects to get all relevant IDs and then run list_bugs sequentially for each one.
What does the `list_sprints` tool actually show? +
list_sprints shows scheduled iterations (sprints) for a specific project. It details upcoming timelines, current progress, and future planned dates for that release cycle.
Do I need an API key to use `list_users`? +
Yes, you must subscribe and provide your Yodiz API credentials. The server uses those keys to run list_users and access all registered team member data.
If I pass an incorrect or non-existent ID to `list_user_stories`, what error message should I expect? +
The tool immediately returns a specific error code indicating the project ID is invalid. It won't try to retrieve data and will tell your agent exactly which ID needs correcting, saving manual troubleshooting.
Does `list_bugs` allow me to filter the results by status (e.g., 'Open' or 'Needs Review')? +
Yes, you can pass a specific status parameter when calling list_bugs. This immediately restricts the output list to only bugs matching that state, keeping your report focused.
When I run `list_users`, what specific identifiers or IDs do I get for each colleague? +
The tool returns a structured list containing the user's full name, email address, and their unique Yodiz internal ID. You use this ID when assigning tasks or mentioning team members.
If I need data from multiple projects sequentially, is there a rate limit when using `list_projects`? +
The server monitors API usage automatically. If you hit an operational threshold, your agent will receive an HTTP 429 error and should pause for a short period before retrying the call.
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.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Clockify
Manage time tracking and projects via Clockify — track entries, monitor projects, and audit team hours directly from any AI agent.
DingTalk
Alibaba's B2B office platform — manage users, departments, send notifications, track attendance, and automate approval workflows.
Fulcrum
Manage field data collection, track form records, and query datasets via AI agents with Fulcrum.
You might also like
Vectara
Empower your agent with Vectara's RAG capabilities. Search corpora natively, execute grounded chats, and manage indexed datasets easily.
CARTO
Empower your AI agents to execute spatial SQL, generate routes, create driving isolines, and bulk geocode directly on CARTO.
Wayfront
Manage your parking operations with digital permits, enforcement tracking, and revenue analytics for parking facility operators.