Codebase memory MCP may not work smoothly in Cursor
In real use, codebase-memory-mcp worked for a while with , but it did not feel smoothly integrated with Cursor. The install succeeded, yet only 8 tools were available inside Cursor.
When asked to index the codebase, Cursor appeared to use its own MCP instead of the tool. That process used up the very quickly.
The lack of hooks made it hard to tell whether the tool was really working as intended. The practical question is whether another MCP works better with Cursor.
Key points
- codebase-memory-mcp installed in Cursor, but only 8 tools were available.
- A codebase indexing request appeared to trigger Cursor's own MCP instead.
- The was consumed quickly during indexing.
- Missing hooks made the setup feel hard to verify.
- A better Cursor- MCP may be needed for this workflow.