I saw a short demo for a Sentry MCP Server a couple of days ago and thought “Hey, I wan’t that for Monti APM”. So today I made Warp build one.
So it’s really fresh and not tested with anything besides Warp itself. It’s already used that new Tool to help with debugging stuff we were working on later this day.
5 Likes
It’s completely vibe coded with warp.dev and took about 2 hours. Vibe coding MCP servers works fine. They are usually relatively small and just have to do a few tasks and you need an agent to test them anyways.
And it’s quite fascinating to have AI write its own tools. When I first tried doing that I used Claude Desktop (with the desktop commander MCP, to allow it to read/write files etc). Claude Desktop with its standard setup has a really bubbly and excitable personality. I was experimenting with having Claude use my obsidian vault at the time and suggested we could maybe access the smart connections obsidian plugin to give Claude semantic search of my vault. It did some research and found a way and then got really excited, wrote a plan how to do it and set it as a top priority task on my kanban.
1 Like
Yeah, I had planned to include him in the announcement but then forgot. There’s probably quite a bit room for improvements.
Nice work Jan-Claude 
. So what sort of things have you been able to do it? Can you share any example usage ?
Quite frankly, I have not really used it since I have been testing it. I am still in the process of figuring out how to use warp.dev efficiently. The workflow is completely different from coding by hand. You do less work coding yourself but you pay for that by having to do context engineering, so your agents know how you want them to do things. I also want to take care of side effects of this type of work. You don’t really know your code as well when you have your agent write it and I think you also loose your edge overall much faster than you think.