| FMRS | 52 / 100 · D | 75 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 |
|---|
| Maintenance | 11 / 20 | 14 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 |
|---|
| Setup experience | 11 / 20 | 15 / 20 |
|---|
| Best for | - Technical artists and 3D professionals on Windows with 3ds Max 2023–2027 who want to automate Max from an MCP client using natural language
- Teams that need to hook 3ds Max scene operations into AI agent workflows (Claude Desktop, Codex, Cursor)
- Advanced users who want to extend their own tools via introspection and MCG/MAXScript
| - Individuals or teams who prioritise privacy and offline operation and do not want data leaving the machine
- Users who share memory across multiple MCP clients such as Claude Code, Claude Desktop, Hermes Agent, OpenClaw, Cursor, Codex and Gemini CLI
- Scenarios that need encrypted storage, a hash-chained audit log and verifiable vault migration
- Users who want low-latency recall, a bundled embedding model and no extra LLM calls inside the memory layer
|
|---|
| Not for | - Users on operating systems other than Windows, or on 3ds Max 2022 and earlier
- Users who do not want an AI client to modify or delete scene content
- Users who only need to inspect 3ds Max files statically without automation
| - Users who need cloud multi-device sync or a hosted team memory service; moving between machines means locking the vault and copying the file
- Users who expect the server itself to run an LLM that extracts facts and decides what to remember; Compartment explicitly keeps no LLM inside and leaves that to the host model
- Users who cannot keep a passphrase safe or who need a recovery path if it is lost, since Compartment never generates a password, seed or recovery phrase
- Deployments that require network transports such as SSE or streamable-http; this server is stdio only and opens no ports
|
|---|
| Required permissions | - Control the 3ds Max scene: create, modify and delete objects and materials
- Read and write scene files and .mat material library files (save, hold, merge, scan .max files)
- Execute MAXScript and Python code inside Max (execute_python requires safe mode off)
- Capture viewport, screen and render images
- Read and write external asset and texture files through installed importers/exporters
- Access the network to search for and download Cosmos assets
| - Read and write the vault file under the user's home directory, by default ~/.compartment/memory.vault, and its sibling settings file
- Access the session directory holding the unlock credential (configurable with COMPARTMENT_SESSION_DIR), which also carries the shared embedding process's Unix socket
- Optionally use the macOS keychain (compartment unlock --keychain is an explicit opt-in, and it survives reboots)
- Write or merge an mcpServers entry into each MCP client's own configuration file, taking a byte-exact backup first
- Install a PostToolUse hook for Claude Code that captures memory files the agent writes
- Serve a read-only dashboard on 127.0.0.1 behind a one-time random URL token
|
|---|
| Risks and side effects | - execute_maxscript and execute_python can run arbitrary code inside Max; execute_python requires safe mode to be turned off, which raises the risk considerably
- Scripted and batch operations can modify or delete scene objects, materials and files, and mistakes may be hard to reverse (some operations have undo and preflight protection)
- Writing .mat files, saving scenes or exporting assets changes files on the local machine
- Integrations such as tyFlow, RailClone and Forest Pack are at different maturity levels (Forest Pack is explicitly marked as work in progress) and may be incomplete or change between releases
- Depends on a native bridge with support limited to 3ds Max 2023–2027
| - A leaked passphrase means the encrypted content can be decrypted; Compartment generates no recovery phrase and cannot recover a lost passphrase
- Enabling the memory_unlock tool places the passphrase in the model's context, which is why it is off by default
- If a 2FA keyfile is lost, for example a USB stick, the vault cannot be opened even with the passphrase
- `export --plaintext` writes the vault as unencrypted JSONL, so that file must be handled carefully
- Memory content can come from untrusted sources; recall wraps memories with a notice that they are stored data and content can be marked quarantined, but the host agent must still treat memory as data to limit prompt-injection risk
- The capture hook and client integration write into the user's own settings files, although the implementation backs up and merges rather than replacing
|
|---|
| Supported clients | Claude Desktop, Codex, Cursor | Claude Desktop, Claude Code, Hermes Agent, OpenClaw, Cursor, VS Code, Codex, Gemini CLI, Cline, Roo Code, Zed, OpenCode, LM Studio, AnythingLLM, BoltAI, Goose, Kiro |
|---|
| Tools | 100 | 14 |
|---|