Data as of
Memory Bank MCP Server for Cursor: Setup & Config
Cursor: Manage project memory files through an MCP assistant using a shared storage root.
What you can do with Memory Bank in Cursor
Choose it for straightforward, project-isolated memory files shared with an MCP coding assistant.
- Find and read an existing project's context files.
- Create or revise memory-bank documents through an MCP client.
Before you start: Memory Bank in Cursor
- Node.js and npx
- An MCP-compatible client
- A configured memory-bank storage directory
This follows the README's Claude configuration. Set the storage root to your directory. Docker is an alternative and requires a host-volume mapping. Review any client auto-approval settings separately from the server launch.
Memory Bank Cursor configuration
Choose Cursor configuration scope
For Memory Bank MCP Server, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.
Add Memory Bank MCP Server to Cursor
Use the memory-bank-mcp entry below in mcpServers. Keep Memory Bank MCP Server's documented stdio connection fields and your other Cursor entries.
Check Memory Bank MCP Server in Cursor
Memory Bank MCP Server: Enable in Cursor’s MCP settings; inspect tools.
Config file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
{
"mcpServers": {
"memory-bank-mcp": {
"command": "npx",
"args": [
"-y",
"@allpepper/memory-bank-mcp@latest"
],
"env": {
"MEMORY_BANK_ROOT": "<directory that will hold project memory banks>"
}
}
}
}Memory Bank tools available to Cursor
Memory Bank's stored tool list documents 5 tools; compare it with Cursor's connected tool list, because the stored list is not a live check.
- memory_bank_read
Find memory_bank_read under Memory Bank in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Read a file from a selected project's memory bank.
- memory_bank_write
Find memory_bank_write under Memory Bank in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- memory_bank_update
Find memory_bank_update under Memory Bank in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- list_projects
Find list_projects under Memory Bank in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Discover projects stored beneath the memory-bank root.
- list_project_files
Find list_project_files under Memory Bank in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Enumerate the memory files belonging to one project.
Troubleshooting Memory Bank in Cursor
- Cursor must find npx @allpepper/memory-bank-mcp@latest (Node.js/npm) for Memory Bank MCP Server. Enable the project/user entry in MCP settings and inspect its tools.
- Review MEMORY_BANK_ROOT for Memory Bank MCP Server before sharing project .cursor/mcp.json; project scope travels with the repository.
- Memory Bank MCP Server uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
- Known limitation: Requires choosing and maintaining a storage directory.
- Known limitation: The documented interface does not include semantic-search tools.
- Known limitation: Sample client settings can auto-approve writes and should be reviewed.
- General Cursor troubleshooting lives in the /clients/cursor guide.
Memory Bank MCP Server — details. Cursor guide