forest_loss — emem, the verifiable memory protocol for the physical world MCP Prompt
forest_loss
is one of 12 prompts on the
emem, the verifiable memory protocol for the physical world
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke forest_loss from your client
- Claude Code emem, the verifiable memory protocol for the physical world Prompt/forest_loss run in your project directory
- Claude Desktop emem, the verifiable memory protocol for the physical world Prompt/forest_loss ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor emem, the verifiable memory protocol for the physical world Prompt/forest_loss ~/.cursor/mcp.json
- VS Code emem, the verifiable memory protocol for the physical world Prompt/forest_loss .vscode/mcp.json
- Zed emem, the verifiable memory protocol for the physical world Prompt/forest_loss ~/.config/zed/settings.json
- Windsurf emem, the verifiable memory protocol for the physical world Prompt/forest_loss ~/.codeium/windsurf/mcp_config.json
- Cline emem, the verifiable memory protocol for the physical world Prompt/forest_loss ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI emem, the verifiable memory protocol for the physical world Prompt/forest_loss ~/.gemini/settings.json
- Grok emem, the verifiable memory protocol for the physical world Prompt/forest_loss .mcp.json (in your project root)
- ChatGPT emem, the verifiable memory protocol for the physical world Prompt/forest_loss Settings → Connectors → Advanced → Developer mode
- Claude.ai emem, the verifiable memory protocol for the physical world Prompt/forest_loss Settings → Connectors → Add custom connector
- LangChain emem, the verifiable memory protocol for the physical world Prompt/forest_loss pip install langchain-mcp-adapters
Other prompts on this server
emem, the verifiable memory protocol for the physical world also offers 21 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.