Server facts
website-publisher-mcp
Project
- Author
- 11cafe
- Repository
- github.com/11cafe/website-publisher-mcp
- License
- Not specified
- Category
- Cloud & DevOps
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 19
- Last commit
- Data as of
Tags
- ai tools
- web builder
- website publisher
Overview
Website publishing in Runbox starts with a remote Debian sandbox equipped with Python and Node.js. AI assistants and agents can create or replace files, inspect their contents, list a directory’s immediate entries, and execute commands while developing or debugging code. The workflow supports projects containing multiple files, including HTML, CSS, and JavaScript. A file write also returns a viewing URL, while the live code editor lets users inspect generated source and make changes to website content.
Publishing follows separate paths for static files and running web servers. The static hosting tool provides a website URL for files in the sandbox and requires an index.html file at its root. For a running web server, the port exposure tool makes a sandbox port publicly reachable and returns a URL for testing. These tools connect code creation, inspection, execution, and browser access within a remote development workflow. The MCP connection uses stdio, with Node.js identified as the integration runtime.
website-publisher-mcp setup notes
- website-publisher-mcp records stdio only; confirm a network transport upstream before planning remote access.
- website-publisher-mcp has no recorded license; confirm reuse terms in its repository.