Which channel when: Web app vs CLI vs MCP vs API vs Self-host
Summary
Six doors lead to the same document engine. Pick by who or what starts the work and where the file may travel, not by habit.
The decision table
| Channel | Who drives it | Where files go | Best for | Needs |
|---|---|---|---|---|
| Web app | You, with the mouse | Documentize cloud | One-off jobs, trying things, visual preview | A browser |
| CLI plugin | You or a script | Your machine (engine runs locally) | Repeatable jobs, folders of files, cron, CI | .NET 10 runtime, a download per plugin |
| MCP server | An AI assistant | Documentize cloud (the assistant passes file URLs) | "Compress this and then summarize it" in a chat | An MCP client and optionally a dmk_ key |
| REST API | Your own program | Documentize cloud | Embedding in an application | An HTTP client; see the caveat on the API page |
| Self-host | Your program or the web UI you host | Your server only | Confidential data, air-gapped networks | .NET 9 runtime or Docker |
| Desktop clients | You, in a native window or terminal | Cloud, or a local/self-hosted engine | Staying out of the browser, optionally offline-ish | Windows 10+, Linux, or any terminal |
Questions that decide it
- Must the file stay inside my network? Yes: self-host, or CLI plugins (they process locally). No: anything.
- Is a person picking the files each time? Yes: web or desktop. No: CLI, API or MCP.
- Is the "caller" an AI assistant? Yes: MCP. It is built so a model can discover tools, read refusals and retry sensibly.
- Do I need to chain more than two steps over many files? CLI plugins in a shell script, or MCP with its batch tools.
- Am I building a product on top? REST API or self-host, plus the plugin contract if you extend it.
Trade-offs worth knowing
- CLI plugins run on your hardware. No upload, no waiting for a queue; but you install the .NET runtime, a license file (or work in evaluation mode) and, on Linux, fonts and
libgdiplus. - MCP and REST are cloud. Your files are processed on Documentize servers and results are available for download links. Treat it exactly like the web app for privacy purposes.
- Self-host trades convenience for control. You run the update cycle, but nothing leaves your box.
- AI-powered apps (abstracts, chat with a PDF, checklists) run in the cloud; some also have a CLI plugin, so check the catalog.
Common mistakes
- Using the web app for a 200-file batch. Use CLI or MCP
ProcessBatch. - Giving an AI assistant files that are confidential, without a self-host. Use self-host and point the clients at it.
- Expecting the CLI to take
--input file.pdf. It does not; see CLI plugins for the folder-based model.
Related
- CLI plugins · MCP · REST API · Self-host · Desktop