Organise client projects
Keep each client’s assets together and give your assistant an explicit destination.
Last reviewed:
Select a destination
Create or open a project in Canvas. With MCP, call memm_list_projects, identify the correct project, and pass its ID as project_id to memm_generate. Use the ID returned by Memm; do not invent one from the project name.
The current connection does not automatically create a named project or remember a default project. When no project is supplied, results can land on the main canvas. Always pass the destination explicitly for client work.
A reusable instruction
Before generating, list my Memm projects and identify Acme Launch.
If there is no matching project, stop and ask me to create it in Canvas.
Use its project_id for every new generation in this task.
Include the project name and ID in your progress updates.
Save downloaded files under ./projects/acme-launch/.
Keep prompts, reference images, outputs, and job IDs together.
Local folders and Memm projects
A Memm project organises assets in your account. A folder on your computer stores local files. They are separate destinations: the cloud Memm MCP does not create local folders by itself. Codex or Claude Code can organise local files when it has access to your workspace.
Keep a small local manifest with the Memm project ID, job IDs, prompts, and downloaded filenames. Reuse the original job and retry key if a request is interrupted.