MCP + image support

Bug Reports
1

Thanks for reporting a bug you have found in Cursor!
Please add the following info to help us diagnose your issue:

:white_check_mark: Check the forum to ensure the issue hasn’t been reported already

None found

:lady_beetle: Provide a clear description of the bug

I was testing out the puppeteer mcp server written by anthropic. When I try and take a screen shot I get a warning saying that images aren’t supported.

:arrows_counterclockwise: Explain how to reproduce the bug (if known)

Just ask it to take a screen shot.

:camera: Attach screenshots or recordings (e.g., .jpg, .png, .mp4).

image
image622×820 67.6 KB

:computer: Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x).
Sequoia 15.2
Cursor 0.45.10

:no_entry_sign: Tell us if the issue stops you from using Cursor.
nope

1 Like
2

The command is npx -y @modelcontextprotocol/server-puppeteer

3

I just tried and got the same.

image
image2182×540 38.3 KB

image
image1234×1690 191 KB

4

I tried adding github as well, but apparently it’s not exporting the tools in a way that cursor can understand…

5

+1 Would love this to work too :slight_smile:

6

The issue here is that the puppeteer MCP server outputs screenshots as base64 data directly to the terminal, rather than saving them as image files that Cursor can reference. This causes the “conversation too long” error since it’s trying to include all that raw image data

You’ll need to modify the server to save screenshots to files instead of outputting them directly. For now you can work around this by having the server save screenshots to a local path and return that path instead of the base64 data

7

@danperks is there a way to read the images from disk in the same way we paste the image into the chat window?

i have an MCP server that saving screenshots of my browser to disk, but I can’t seem to parse the image in the right way for the llm to see it

8

There’s no way to use an image produced by an MCP server in the Agent right now, except without manually adding it yourself from the disk!

This is a good idea though, will pass to the team.

3 Likes
9

@danperks thank you thank you!

imo this is the last missing piece of the agent loop.

Cursor agent is amazing at writing server code and checking itself, but if you guys add this one feature, you’ve basically built a Devin capable of fully autonomous full-stack web development right into the IDE.

Really looking forward to this

1 Like
10

capabilities: {
resources: {
templates: [“file://${path}”]
}, // Enable resources capability with templates
tools: {}, // Keep tools capability
}. When coding for MCP server if you support “resource” templates and we can send screenshots as resources. that would still be honouring MCP and give us that image reading abilties

1 Like
11

I’m having the same problem with a tool I created to manage Android devices and do UI automation and other tasks. Everything works amazing, except for screenshots. Any time a screenshot is requested, Cursor says the conversation is too long and fails. I’m using the MCP Python SDK and the Image type. I tried converting from PNG to JPG to reduce the size, but the conversation too long error persists. The size of the image is <300K so it should be totally fine.

This is definitely a missing piece in the agentic workflow. I’d love it if this got fixed!

image
image786×570 30.1 KB