Huge memory occupation by sequentialthinking MCP #2912
Description
Describe the bug
After using sequentialthinking for a few hours, the RAM gets hogged up by this MCP server as much as 10GB+ RAM or more (I had this much RAM available, so..). But I doubt it is the Planning, because 10+ GB of Text is a huge amount of text, I DON'T THINK it was the TEXT. I strongly think there is a memory leak.
To Reproduce
- Use this MCP for a few (6-8) hours for frequent and long planning
Expected behavior
The memory should be freed after a job is done, or the memory should be offloaded to a disk space after a certain period of time. This should also help with persistent planning (Maybe, add a new tool for this).
Additional context
I have deployed this MCP as a distributed, standalone Docker container.
I love this MCP, a really great project. MANY MANY THANKS to the modelcontextprotocol Team
Regards