us, which is awesome. Now, I get this question, "Isn't MCP 6 months old and it's dead now?" Now, a lot of people on the internet have opinions that change every other day, and some people were saying that, well, you can do a lot of stuff with MCP just with command line tools. I really think MCP is still maturing. There's a lot uh a long road ahead for it, especially with some of the security stuff it's doing. I would keep an eye out for MCP, but one of the main reasons I like it, especially for the Spec Driven Development Flow, is you can have something like in Jira or Asana, all your tickets, all your uh large requirements docs, and then you can have it being pulled into your Spec Driven Development Flow when it creates your specs, which makes it much easier to work with. So, if you have a product manager that has actually written a requirements document, you can pull that in. And uh it just makes a little bit easier. And I'm I'm talking about any any kind of project management service. And grab technical details for it. You can also put additional rules in your steering or your agents.md files that tells it, so if you're using Spec Driven Development Flow, make sure you grab the information out of this MCP server. And that way it knows where to look. Or you can just specify it in the first step, like, "Hey, look at this MCP server when you create the requirements."