Replies: 1 comment 2 replies
-
|
Hi @alanbork, thanks for raising this and I totally get your frustration. The servers repo isn't being ignored, but you're right that it's under-resourced at the moment. It shares maintainers across several other repos and discussion forums, so response times can be very uneven. I left a comment on the issue you linked (modelcontextprotocol/servers#3281) to help figure out whether this is a problem with the Desktop Extension version of the filesystem server or the repo version, since they're maintained in different places. That distinction matters for getting the bug routed to the right team. If it turns out this is specific to the Claude Desktop extension, the best path is through Claude support. For issues with the open source server code in this repo, filing there is still the right place and we do monitor it, even if the turnaround isn't always fast. Also feel free to ping me and other maintainers if an urgent issue isn't getting attention. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Pre-submission Checklist
Question Category
Your Question
Myself and several other people have experienced consistent problems with the filesystem extension being completely broken. I took the step of filing an issue against the repo here on github but skimming the 200+ issues it seems that's writeonly storage/ a trash bin not actually monitored by anybody. Any suggestions of a place to file this issue where it's actually going to be seen and acted on? Or do they pretty much ignore bug submissions in the vein of move fast and break everything.
modelcontextprotocol/servers#3281
Beta Was this translation helpful? Give feedback.
All reactions