You can host Mossy in server mode or static mode. Both include the same web tools. The main difference is whether you also need API and MCP endpoints for scripts and assistant integrations.
Compare the modes
Choose a mode based on how you want to use Mossy and where you want to host it.
| Feature | Server mode | Static mode |
|---|---|---|
| Web tools in your browser | Included | Included |
| API endpoints | Included | Not included |
| MCP endpoint | Included | Not included |
| Hosting | Node.js or Cloudflare Workers | Any web server or hosting service that serves static files |
| Docker image | ghcr.io/get-mossy/mossy:latest |
ghcr.io/get-mossy/mossy:latest-static |
Server mode
Server mode serves the web interface and exposes API routes under /api/v1/ and the MCP endpoint at /mcp. Choose it if you want to call tools from scripts or connect an MCP client, such as an assistant.
The web tools still run in your browser. Requests made through the API or MCP run on your hosted instance instead.
The default Docker image runs Mossy with Node.js. Mossy also supports server builds for Cloudflare Workers.
Static mode
Static mode produces HTML, CSS, and JavaScript files that you can serve without running a Mossy backend. The web tools run in your browser, just as they do in server mode.
You still need a web server or static hosting service to deliver the files. The static Docker image includes Nginx for this purpose, so static mode doesn’t mean you must avoid Docker.
Choose static mode if you only need the web interface. It doesn’t expose API or MCP endpoints.
Next steps
Follow the Docker Compose installation guide to run either mode. The guide uses server mode by default and explains which image tag to use for static mode. To install without Docker, follow the prebuilt release installation guide.
The mode is selected when Mossy is built. To switch an existing deployment, use the corresponding build or Docker image; changing a runtime environment variable doesn’t switch modes.