I’m trying to use the MCP server memory with n8n but I’m running into some issues. I’ve set up the add_observation node tool and created a workflow, but I keep getting an error message. It says:
Failed to execute operation: Failed to execute tool 'add_observations': MCP error -32603: Cannot read properties of undefined (reading 'includes')
I thought maybe using it as a node instead of a tool would help, but no luck. The error persists. I’m starting to wonder if there’s a problem with my JSON, but I can’t figure out what it could be. Has anyone else run into this problem or know what might be causing it? I’m pretty stumped and could use some guidance on how to troubleshoot this.
Any help or ideas would be really appreciated. Thanks!
I’ve been down this road before, and it can be frustrating. From my experience, this error often crops up when there’s a mismatch between the data structure you’re sending and what the MCP server expects. One thing that helped me was to double-check the schema of the observations I was trying to add. Make sure all required fields are present and correctly formatted.
Another potential culprit could be network issues. I once spent hours debugging my JSON, only to realize my VPN was interfering with the connection to the MCP server. It might be worth testing your connection or trying from a different network if possible.
Lastly, don’t underestimate the power of logging. I found adding detailed logs before and after the add_observation node helped pinpoint where exactly things were going wrong. It’s a bit of extra work, but it can save you a lot of headaches in the long run.
Hang in there - these integration issues can be tough, but they’re usually solvable with some persistence!
I’ve encountered this error before when working with n8n and MCP server memory integration. One often overlooked aspect is ensuring your MCP client version is compatible with the server you’re connecting to. Mismatched versions can lead to unexpected behavior and errors like the one you’re seeing. Additionally, double-check your MCP server configuration, particularly the memory allocation settings. Insufficient memory allocation can sometimes manifest as this type of error. If you’ve verified these and are still facing issues, consider reaching out to n8n support or checking their documentation for any known conflicts between the MCP client and recent n8n updates. Troubleshooting integration errors can be tricky, but methodically ruling out potential causes usually leads to a solution.
hey amelial, i had a similar issue. check ur json syntax carefully and also verify the mcp server is live. even small typos can cause this error. hope this helps!