MemPalace MCP not working in Cursor? Fixes

Passed It worked in our test on Oct 22, 2026. Below is the exact setup we used in Cursor (2026.10.19-6bbf2c4), every error we saw, and what to check, all from our own run log.

Date tested: · From our harness, not the maker’s claims · How we test

1. Use the install config we tested in Cursor

{
 "mcpServers": {
  "mempalace": {
   "command": "uvx",
   "args": [
    "--from",
    "mempalace",
    "mempalace-mcp"
   ],
   "env": {
    "MEMPALACE_PALACE_PATH": "/workspace/timmy/harness/sandbox/mempalace"
   }
  }
 }
}

Replace any <YOUR_…> placeholder and local test paths with your own. Every client’s tested snippet is on the MemPalace page.

2. Check that Cursor connects to it

In our run the connect check was OK (connected in 1.4s). Our check output:

mempalace: ready

3. Confirm the tools are visible

Cursor listed 47 tools from this server in our run (the protocol check found 47). Fewer or none usually means the server did not start; check the config above.

Errors we observed

  • agent task: recall across sessions (tool error during the run): {"error": {"error": "Tool execution error", "readToolDefReminder": "MCP error -32602: Unknown parameter 'embedding_model' for tool mempalace_search", "systemReminders": [{"body": "The namespace rejected these arguments as invalid. Before retrying, call GetDynamicTools with {\"namespace\":\"mempalace…

Quoted from our run log. Secrets redacted. We list only what we saw.

More help

MemPalace: all results and setup · Full Cursor run · General Cursor MCP troubleshooting

Featured