Guide · Cursor
Cursor’s agent works from your code. When the problem is something you can see on the running page, the clearest instruction is the element itself. Yocoolab lets you click it in the browser you already use and hand it to Cursor over MCP, with the screenshot, selector and computed styles attached.
Cursor reasons well about code, but "the spacing on the pricing card feels off" describes a screen. The agent has to translate that back into a component before it can change anything.
Cursor’s agent can drive a browser of its own: its docs list tools to navigate, click, type, scroll and take screenshots. That helps the agent check its own work. It is a different job from you, or a teammate, pointing at the element you mean.
The person who spots the problem is often a designer or PM who is not in the editor. They need a way to hand over "this element, on this page" without opening Cursor.
With the Yocoolab extension for Chrome, Edge or Firefox, anyone on the team clicks the element on the live page and writes what should change. The comment keeps a screenshot, the CSS selector, DOM path, attributes, computed styles and the page URL.
Send to Agent queues the thread for your agent. Cursor, connected to Yocoolab over MCP, reads the thread with get_thread_context, which names the repository, the element and the change, and finds the code.
The agent makes the change, opens a pull request and moves the thread to In Review, where a person signs off.
Visual problems live in the rendered page, so that is where the instruction should start. Pointing at the element replaces a paragraph of description, and it works the same for the developer in Cursor and for the designer who never opens it.
Click Add to Cursor on app.yocoolab.com/connect, or put the address https://app.yocoolab.com/mcp in ~/.cursor/mcp.json. Then click Connect in Cursor’s MCP settings, sign in to Yocoolab and click Allow. There is no token to paste.
Localhost, staging or production, in Chrome, Edge or Firefox. Write what should change.
Then ask Cursor’s agent to work on your Yocoolab threads. It gets the screenshot, selector, DOM path and styles, and finds the source.
The thread moves to In Review. Check the change on the page, then resolve it.
If you are the only person on the project and already work with the app open beside Cursor, describing the change directly in Cursor’s chat may be enough.
Facts about Cursor on this page come from Cursor docs: browser, checked October 2026.
Yes, with Yocoolab. Install the extension, connect Cursor with Add to Cursor on app.yocoolab.com/connect, pin a comment on the element and click Send to Agent. Cursor reads the screenshot, selector, DOM path and computed styles over MCP.
Yes. The extension works on localhost, staging and production pages, and in Chrome, Edge and Firefox.
Yes. Anyone in the workspace can pin a comment. Sending it to an agent needs AI access, which workspace owners and admins have by default and can give to others.
No. Cursor still writes the code. Yocoolab is how the element on the live page reaches it.
Pin a comment on the element in your live app; your coding agent gets the screenshot, selector and discussion, and opens the PR for a person to review. Free for your whole team, in beta.