I wanted an MCP server without the need for a browser extension so I made this one recently which currently supports screenshots and getting the browser console log. Iām not suggesting itās better than the other ones (and it is very new) but it does allow me to tell Cursor to verify the results in an actual browser (it uses Playwright) and also to e.g. tell it to fix the console errors on a page. Itās also possible to specify a specific CSS selector to focus the screenshot on.
100% agree here. We needs a built-in feature like this.
You could maybe have built this using AI already, sprint cycles of 2 weeks you could at least scaffold it, two modular UIs that see upstream and downstream dataflow with nodes that represent storage, auth etc. a bit like n8n. The other one can show the UI and you can select DOM elements just like that, or take snapshots and it knows what you are referring to.
Our Lord and saviour @leerob will surely make this happen, given his Next.js experience. 
Yes, heās good at it, letās hope there will be a lot of useful things.
My early reaction here is: this would be helpful and useful, but also at the same time, the current way of working isnāt that bad!
Basically saying: lots of people have opinions about their editor/browser relationship. Itās hard to find the right solution for all of them.
I do think this is something weāll explore more earnestly in time, but also wanting to set the expectation itās not something weāre immediately working on.
Thanks, I didnāt know this existed. But it seems to have no integration with Cursor agent.
Ultimately iād like Cursor agent to be able to have access and communicate about UI without having to provide screenshots when doing frontend work
Considering how AI interactivity with images/video is developing now, this would be really cool. Especially along with a browser thatās built right into the Cursor, with all the data as contextā¦
Sounds too sweet
This is a must, cursor!
I think it would be great if Cursor has a visual preview on what the product would look like, just like how lovable.dev has
like i wish that was a default thing so it would be easier for the user to see what is going on instead of jumping from A to B to C to D to E in order to see a preview of the product.
What? I didnāt know that!
That didnāt work. The feature needs to be a default. I need a feature that goes from point A to point B. No in between shenanigans of complications.the UI needs to make it easier to get to, it just needs to work.
Like come on. Adobeās Dream weaver was already ahead of cursor on this! Lovable is ahead of cursor on this! Why is this too complex for cursor?
Yes, youāre right, the functionality is limited, but itās not our development. Itās originally integrated into VS Code. Maybe in the future, weāll create our own solution for this.
+1 for this!
Cursor is surrounded, yesterday Bolt has introduced it too:
I use Cursor as my main Ide itās incredibly powerful and makes my development smooth. But thereās one key feature missing that really slows things down the ability to preview web apps and inspect DOM elements directly inside Cursor.
Right now, I constantly switch over to Windsurf just so I can inspect an element, and send it to the chat for changes. Cursor has everything else I need, but I have to leave it just to do this one thing. It breaks the flow, wastes time,
If Cursor could include a live web preview and let us click elements to inspect and send them straight into agent for editing, that would be a great. It would massively speed up debugging and design work, and really unlock more of Cursorās potential.
I know a lot of us using Cursor would benefit from this. Letās make it happen team cursor
The ability to preview your web app inside cursor, with the ability to inspect DOM components, and send that component code directly into Composer for the agent to iterate on.
Without this, we have to rely on sending screenshots, which is not always precise or clear with its understanding.