When is the PR to fix the @modelcontextprotocol/server-memory MCP server schema error? Seems like a simple thing taking ages. I like to share the memories between claudecode and cursor but this has been broken for seemingly forever due to a simple schema validation error which I see was fixed in a PR but it’s still not merged?
Hey, thanks for the report. The issue with @modelcontextprotocol/server-memory is an upstream issue in the Model Context Protocol repo, not in Cursor. Cursor integrates MCP servers, but it doesn’t control their development or when PRs get merged in their repo.
If there’s an open PR in the modelcontextprotocol/servers GitHub repo, it’s best to ask about merging it there, in their issue tracker or discussions. Cursor uses those servers as-is.
If you want a workaround, you can try:
- Using a different memory MCP server (there are community alternatives)
- Building your own version with the patched change, if the PR already exists
Can you share the exact error text and the PR link? That’ll make it clearer whether anything can be done on the Cursor side, or if it’s purely an upstream problem.
Ah i figured the cursor team would be working with them to fix the bugs, as it works in other agents. If it’s just in their repo and there’s nothing you can do about it then we can delete this. I guess I incorrectly assumed you were working with them on it since it works everywhere but cursor for me at the moment. I guess i can look for an alternative and copy the memories over. thanks
Schema error, PR3094 fix(memory): strip type field from entities/relations in loadGraph by jared03 · Pull Request #3094 · modelcontextprotocol/servers · GitHub