ShareBox

What ShareBox does

The ShareBox MCP server connects an AI agent to a self-hosted platform for publishing small web applications. An agent can create a tool, publish it, and help configure access through the ShareBox instance. Each published tool receives its own HTTPS address, and republishing updates that tool while preserving its data.

ShareBox supports sharing with individual email addresses, all Google Workspace accounts in a domain, or anyone who has the link. Each share can grant either use or manage access. Visitors authenticate with Google, and the tool receives their name, email address, and role. The platform applies permissions on the server, including ownership rules for stored records.

This fits the 💻 Developer Tools category because it provides an agent-facing workflow for creating, deploying, and administering small web tools rather than serving as a general hosting provider.

How it works

A ShareBox installation runs on an Ubuntu 24.04 Linux server. Caddy handles HTTPS, while the platform provides the Google login flow, permissions, dashboard, API, and request gateway. Every request passes through that gateway before reaching the published tool.

Each tool runs separately in a gVisor sandbox using workerd. Its code is read-only at runtime, and CPU, memory, and process limits can be applied. Tools cannot access other tools, the host, the platform, or the public internet. A tool receives its own SQLite database. Static applications can use the supplied browser SDK, while applications with server code can use direct SQL access.

The platform also includes a web dashboard for sharing, logs, activity, status, suspension, and deletion. Nightly backups are scheduled during installation, with optional encrypted copies to Google Drive.

Setup and configuration

The ShareBox MCP server requires an Ubuntu 24.04 server with ports 80 and 443 available. The README states that 2 GB of RAM is enough to start. You also need a domain for the platform, a domain for published tools, and a Google OAuth client. DuckDNS or a Cloudflare-managed domain can be used for the tools domain.

Installation is performed from the repository with the supplied installer. It installs Docker and gVisor, asks for domain and credential details, checks DNS, ports, and firewall configuration, builds the components, starts the services, and schedules backups.

On the client machine, install Node.js 20 or newer and the ShareBox CLI, then authenticate with sharebox login. Connect an agent by registering sharebox mcp as an MCP server. Claude Code is shown in the setup instructions; Windows users need to invoke the command through cmd /c.

Tools and capabilities

The ShareBox MCP server includes a built-in sharebox_guide for agents. The surrounding CLI workflow supports initializing a starter project, publishing it, and sharing it. A project can contain static files in public/ and an optional worker.ts for server-side behavior.

Published tools can use the ShareBox SDK to identify the current user and work with collections. Records expose ownership and editability information. Users with use access can edit their own records, while users with manage access can edit all records, subject to server enforcement.

Limitations and notes

ShareBox is a single-server deployment. The README estimates roughly 25 simultaneously running tools on a 2 GB machine, and stopping idle tools is planned. Published tools cannot currently call external APIs because they have no internet access or secrets; an egress proxy is planned.

Google is the only supported sign-in provider. Publishing is restricted to email addresses listed in CREATOR_EMAILS. The interface is available in English and Italian, with other languages not yet included. The project is described as young and currently runs on the author's private instance.

ShareBox is licensed under GNU AGPL v3 or later. If a modified version is used to provide a service, its changes must be made available to users of that service.