plopino/plopino-mcp

CLI: publish with one command
login prompts for an email and a hidden password. Create an account on the website
first if needed. Login claims available anonymous uploads made with this CLI's saved
identity, reports how many were claimed, and saves a session for future uploads.
An existing PLOPINO_TOKEN overrides the saved session for publishing.
For Google/GitHub-only accounts, use an API token for future uploads; CLI password
login requires an account with a password.
Cookies are stored per server origin under ~/.config/plopino/, with owner-only file
permissions. Override the directory with PLOPINO_CONFIG_DIR. Keep this directory to
retain the ability to claim anonymous uploads. Passwords are never stored. Logging out
revokes the session but preserves the anonymous identity. Browser and MCP sessions are
separate: logging in on the website alone does not claim CLI uploads.
For non-interactive login, use login --email you@example.com --password-stdin, supplying
the password through standard input from your secret manager. Do not pass passwords as
command-line arguments. --json gives structured results and errors; errors exit with
status 1. Default publishing writes only the URL to stdout and status to stderr.
Directory uploads skip .git, .env*, node_modules, .ssh, .aws, and symbolic links.
Other files are included; publish the output directory you intend to share. A single
explicitly selected file is uploaded as requested. Symlink inputs are rejected.
CLI commands for the same server cannot run concurrently; after a forcibly terminated
process, the next command identifies any stale lock to remove once no command is running.
For development before the npm release, replace npx -y plopino with
node /path/to/boards/mcp/index.js in the examples above.
MCP
MCP server for Plopino — lets an AI agent publish what it just built
and hand back a public link, without the user touching a browser.
Documents are first-class: Word (doc/docx), Excel (xls/xlsx) and Markdown
render as readable pages, code and data files get syntax-highlighted previews, and images
and video display inline. The recipient opens a link; they never download a file.
Tools
| Tool | Use it when |
|---|---|
| publish_page | You have the content as a string — generated HTML, or a Markdown / CSV / code document. The filename decides how it renders: leave it at index.html for a page, pass report.md and it renders as a document. |
| publish_path | The page needs sibling files (CSS, JS, images), or you are sharing something that is already on disk — including any document, and including binary formats (docx, xlsx, pdf) that cannot be sent as a string. Point it at a directory and the structure is preserved — no need to zip first. |
| publish_files | Remote endpoint only. Same job as publish_path for clients that cannot hand over a local path: you send the file contents inline (a relative path plus its content, per entry). |
Both take an optional update_url: pass a link returned by an earlier publish and that page's
content is replaced **while the link stays the same**. This needs a token (see below).
Publishing is **anonymous by default**: no account, no configuration, no API key. The returned
link is public; without a token the page is kept for a month, with a token it is permanent and
can be updated in place.
Anonymous creates also return claimUrl. It is a private browser link for the publisher:
open it yourself, sign in, and confirm the claim to keep that page in your account. Do not
append it to the public URL or share it with page viewers. JSON output includes it as
claimUrl; human output prints it on stderr for CLI publishes and inside the MCP tool result