How long it has been broken for months now..
I don’t understand why they break features while making more and more ■■■■■■ UI.
I think it broke in September 2025. That is the last time I can remember seeing @Docs behave correctly, and getting optimal results with third party libs. I did not realize it was broken at first, until I realized I was really spinning my wheels trying to solve certain tasks with libs or frameworks that were never that challenging before. Then I noticed that the classic doc index refernces that the agent usually spit out when it queried the docs, were no longer showing, and when I researched the thinking cycles in detail, it was clear that the agent couldn’t find or use the docs feature, that it would try using MCP queries (which are ALSO broken, BTW, the agent cannot seem to query the installed MCP servers dynamically, even though there is support for that in Cursor), then it would try web searches, which are not even remotely as effective.
From April through August, Docs seemed to work great, and it was one of the key reasons I fell in love with Cursor early on. Docs REALLY amped up the agents abilities by having pre-embedded documentation indexed and ready to go, so the model could gather task-explicit knowledge about how to use third party…anything. Libs, frameworks, terminal commands, if you could find docs for it, @Docs would supercharge the agent. The agent has honestly been pitiful without it….so it blows my mind, why they just left the feature to ROT for so long… It is one of their biggest selling points, I don’t think anyone else has anything like it. It improves correctness, accuracy, efficiency, reduces cost (fewer tokens), etc. They should fix this, and SELL CURSOR by touting the power of @Docs. Just boggles my mind why they don’t…
Oh I was wondering if it was just me, where it never uses any of the MCPs I had set up. Seems to be broken for me as well. I wonder if it’s somehow related to the docs problems. Somehow these things aren’t visible to the agents even when they are supposedly set up properly.
I actually was wondering if the Docs problem, was actually an MCP support problem in Cursor. I THINK (haven’t been able to get confirmation) that the @Docs feature in Cursor is actually an MCP itself (I think it would have to be, for the model to be able to use it, right?) So if there is a fundamental issue in the MCP capabilities of Cursor, I could see how that could affect the model’s ability to use MCPs.
I have been able to get Cursor to use MCPs, but, I don’t think it is using them properly, as it always seems to have to meander and figure out how to (which I can see in the thought cycles), before it actually invokes any MCP commands. I’ve noticed that, the only way the AGENT/MODEL can figure out how to use an MCP, rather than using the explicitly designed MCP querying tools (which are what’s broken in Cursor, or at least part of what’s broken), is for it to query the available “tools” in Cursor. When you enable an MCP, the list of MCP commands get added to the available tools in Cursor. Once the agent queries that, it will usually (but not always) be able to use the MCP.
I have had to be very explicit about how I reference the MCP I need the agent to use, so that it can find the relevant “tools” when it finally searches for them. If I tell it to use an mcp, but the command names are somehow dissimilar from the mcp name, the agent often won’t be able to find them. FURTHER, there is an explicit MCP command count limit in Cursor, and if the total number of ACTIVE MCP commands surpasses that limit (not exactly sure what it is), then even though the MCP commands show up when the agent queries the “list of tools”, it simply cannot use them…so you have to make sure you disable not just MCP servers, but if you have a single MCP server that just has too many commands (i.e. Github!!!) then you have to disable individual commands until the total number is less than the Cursor limit on MCP commands….
Cursor has some VERY SEVERE, FUNDAMENTAL issues…!!! 
UPDATE: As of version 2.3.41, the docs seem to be (tentatively) working again? Interestingly, I noticed it when I gave it a prompt that did NOT include the @docs mention - it just knew to search in the appropriate docs for that particular problem. The agent said something like “searching through docs for [X]” as an explicit tool call while doing its thing - the first time I’ve noticed it doing that in several months. This is encouraging!
Overall, if this is the direction they want to take it, where you don’t need to explicitly point to the docs you want, and its smart enough to know where to look in most cases, that is a positive development, as one of my annoyances with the docs feature even back when it did work was that it was tedious to have to include @docs every single time you’re working with some library etc. I do think that they should still let you explicitly point to a set of docs though in cases where it otherwise would struggle, kind of like there’s still some cases where you explicitly need to point it to specific files or folders.
Hopefully this wasn’t a fluke and the feature has geniunely been fixed. Not holding my breath given how much things keep breaking lol.
I can confirm this is not working in 2.3.41, i attach the specific docs, it is indexed and working, i can see the indexed pages in cursor settings, but agent cannot visit the site or it just never does, instead it greps the files in project folder and does not do anything with the docs, it tries looking for an mcp server for some reason but does not find anything. it knows the name of the docs, but nothing actually happens with it. frustrating.
i noticed similar behavior when i paste direct links to chat or just ask agent to lookup docs, sometimes it does, but mostly just ignores it and does not do any web searches.
Don’t let the agent fool you. The agent fooled me, as it would say similar things, which is why I wasn’t entirely aware the Docs feature was broken until about a week or so after it actually broke. The agent can be very deceptive a lot of the time, and if it “says” its searching docs, its not searching docs. The @Docs feature had VERY EXPLICIT functionality, and it was utterly clear when it was working before, as it would actually drop little badges for each indexed “chapter” of the docs that it was referencing for the current prompt. If you do not see those badges, then @Docs is not working.
Yeah man.. still broken.
Yeah it usually does web-search of docs that’s ■■■■■■■■■ Why index docs if it needs to web search.
I find myself on these Cursor forums surprisingly often and I get the feeling that Cursor either A) doesn’t really pay attention to them or B) maybe they do, but their customer service is spectacularly 
Either way, January 30th, still broken 