Yodiz MCP for AI. Ask about any sprint or story status.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
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.
What your AI can do
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.
Gathers a master list of every agile workspace you've set up in Yodiz.
Retrieves the high-level strategic features (epics) that define what an entire product line should achieve.
Lists all planned sprints or timeboxes for a given project, showing when they start and end.
Provides detailed lists of specific requirements (user stories) tied to a numeric project ID.
Collects technical debt items and bugs for any defined project, helping QA track down flaws.
Returns a list of all users in your workspace, giving you IDs needed to assign tasks or mention colleagues.
Ask an AI about this
Waiting for input…
Yodiz: 6 Tools for Agile Project Management
Use these tools to pull structured data on every element of your agile workflow—from high-level epics down to specific users and bugs.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Yodiz on VinkiusList 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...
List Users
Lists every registered team member in your workspace, providing IDs needed for assignments.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
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 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ 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
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 connection provides 6 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
It's a nightmare trying to piece together project status from multiple dashboards.
Right now, checking on development progress means jumping between the main board view, then clicking into 'Sprints,' finding the correct iteration ID, and then running a separate report for bugs. You spend time copying IDs, navigating deep menus, and constantly cross-referencing which project you're even looking at.
With this MCP, your agent handles all that complexity. You just ask, 'What are the top 10 user stories for the next sprint?' It pulls the data from `list_user_stories` and `list_sprints`, presents them cleanly, and gives you a single answer without making you click anything.
See the full project scope using list_epics.
Today, if leadership asks for the 'big picture,' you have to manually gather every related story and epic from different sections. It’s a huge manual effort that takes hours just to compile a simple report showing strategic alignment.
Now, calling `list_epics` instantly surfaces those high-level features and strategic goals. You can show the executive team exactly how the current bugs or stories fit into the overall roadmap—in seconds.
What your AI can actually do with this
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.
019d7626-009c-713d-a3af-0a6c1421e5c6 Here's how it actually works
The bottom line is you get instant, filtered access to complex project data without ever touching the Yodiz web interface.
Connect the Yodiz MCP and provide your API credentials through your preferred AI client.
Tell your agent what data you need—for example, 'Show me all bugs for project 102' or 'List all sprints for this quarter.'
The agent runs the necessary tool calls and returns a structured list of projects, stories, or issues right in your chat window.
Who is this actually for?
Product Owners who are tired of chasing status updates across multiple dashboards. QA Engineers who spend too much time manually filtering bug reports. Scrum Masters who need a single source of truth for sprint progress.
Checks sprint progress and audits the backlog to ensure the team is hitting its goals without manual board reviews.
Pulls epic details and user stories quickly to keep stakeholders aligned on the product's overall roadmap.
Runs checks across different projects to track bugs and technical debt items without having to manually filter project IDs.
What Changes When You Connect
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.
See it in action
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.
The honest tradeoffs
Using project names only
Typing 'Show me the bugs on API Gateway' and waiting for an error because the system needs a specific ID.
Always let your agent use list_projects first to get the numeric ID, then pass that ID when calling list_bugs. This guarantees accuracy.
Trying to track all data at once
Asking 'What's happening with everything?' and getting a massive, unreadable dump of every story, bug, and epic.
Be specific. If you only care about bugs in the Mobile App Redesign project, run list_bugs and specify that project ID.
Ignoring team structure
Trying to assign a task without knowing who is available or what their exact username is.
First, call list_users. This gives you the full directory of colleague IDs needed for accurate task assignment.
When It Fits, When It Doesn't
Use this MCP if your job involves coordinating work across multiple interconnected agile components: stories, bugs, sprints, and epics. You need to answer questions like 'What's blocking Sprint 25?' or 'Which users own the API Gateway bugs?'. Don't use this if you simply need a basic list of tasks; for that, a simple ticketing system might suffice. However, because this tool manages relationships between projects and roles (e.g., which user owns which bug), it’s best for complex coordination and reporting. If all you do is track individual records, stick to the core Yodiz app. When you need cross-functional data visibility, use this MCP.
Questions you might have
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.
We've already built the connector for Yodiz. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 6 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.