It seems that MCP resources is not working in the latest version 0.46.9. And I return back to 0.46.8 it’s ok.
same here
2 Likes
ditto
1 Like
mcp resources were causing more problems than benefit, we will be adding them back as at mentions in composer rather than individual tools for agent, does this work for people?
1 Like
What is the recommended way to serve static content to the agent then? Same as before, just swap out the @mcp.resource annotation with the @mcp.tool one? 
also curious how this will work then? the goal is to avoid typing all the time the same strings and mcp allows AI to figure out what part can provide a tool, resource, prompt.
There are now thousands of mcp servers suporting this and its becoming a standard for AI tools. In fact so many are adding this in clients and servers. some are even building it in by default nowadays as it does not require big changes to APIs.
1 Like
They were very, very useful for us and I would prefer the option to choose per project how they’ll be used.
Does this mean that “resources” functionality area within the MCP Servers section is non-functional right now?
I spent a few hours debugging before deciding to check the forums.
Do we plan in the future to properly communicate when features are removed from your product via the changelog, or is the expectation to continue checking forum posts for the most up to date information about what’s actually in each update? There is no information about Resource removal in any of the changelog updates as of 10:15AM AST.
6 Likes
mcp resources were causing more problems than benefit
Can you explain these problems further?
In my experiments and debugging, some static resources are easier and more convenient to be called as resources than as tools.
They were implemented as just tools so if someone had 200 resources you’d have 200 tools and break the entire request
I apologize for the lack of communication here i think they were added in 46.x and removed in 46.y and assumed no one was using them yet (ive never seen them mentioned)
In the future we’re going to more careful about rolling out new features until they’re really dialed in, this one wasn’t thought through
1 Like
By this time the server should really be using resource templates already to avoid exactly that kind of breakage. I’m pretty sure that’s why this feature is part of the protocol.
Cursor has a lot of influence in the AI editor domain, so for me personally that’s the platform to focus on when making devtools, including the ones that utilize MCP 
To this end I was just using what’s available right now.
And besides, resources and resource templates is how you are supposed to serve static content to agents within the MCP realm, as far as I understand. Using tools for that is kind of a subversion of the protocol.
@msfeldstein I have to say, Cursor’s new version often makes significant changes to existing features and pushes them to users’ devices without updating the changelog or notifying users. This has happened far too many times. Forum moderators apologize in scattered posts, but the information is fragmented, and the official documentation remains outdated. As an enterprise user, we’re building internal services based on MCP, and changes like these have a major impact on our plans. If it weren’t for this post, we might have only discovered the issue much later. I sincerely hope Cursor puts more effort into transparency and communication. I completely understand how busy the Cursor team must be, and I truly love Cursor, but this is critical and the current approach needs to change.
2 Likes
Isn’t that the reality of zerover though?
Yes that works well for me. It’s a sensible distinction between tools & resources imo.
Tools → model controlled
Resources → user controlled
That’s kind of the distinction they make in the official MCP docs as well.
Looking forward to working resources support! But please, make a note somewhere if you toggle a feature off again, spent multiple hours debugging this today.
We’re working on improving our change management (telling users about updates) and know its super lacking. Team is growing a lot so i have faith we will be much better about this shortly
1 Like
I tried it as well, but I don’t get any feedback that is available or something like this. it just looks like plain text. is there something that I miss?
@msfeldstein Is there any way to enable MCP’s in agent chat with the new version, or do I need to downgrade to the 0.45 until this is addressed in a different way in a future update? Having MCP’s available was a huge time saver and they were working well for me. I didn’t realize that upgrading would disable the feature. Thanks!
I agree with this. I know we’re on zerover but we’re also paying customers and a heads-up would be nice when major features are removed! I don’t mind staying on 0.45 but this did cost a bunch of people a couple hours each to figure out, because the way MCP’s got disabled was to simply show “No resources available” in the UI, which wasn’t super obvious.
1 Like
How long approximately we need to wait?
any timeline for when this will be released? they were part of the tool I built and unfortunately they don’t work anymore. downgrading is also not a solution as I can only downgrade to the latest previous version where the resources were already removed.
wait is this disabled, i see it in the app, but keeps saying no resources, couldn’t figure it out, and mans just disabled it without telling anyone?