plopino
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLOPINO_TOKEN | No | Optional. Publishes to your account: private boards, in-place updates, no per-IP rate limit. Create one at plopino.com/b | |
| PLOPINO_BASE_URL | No | Base URL of the Plopino instance. Set this to point at another instance (e.g., self-hosted or local). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| publish_htmlA | Publish an HTML page to a public URL. Use this whenever the user asks to share, send, publish, or "give me a link to" a page — for example a dashboard, report, chart, or interactive page you just generated. Returns a public link that opens on any device; no account or configuration needed. Anonymous pages are kept for a month — with a token, storage is permanent and the page can be updated in place. Prefer this over telling the user to save the file and upload it somewhere themselves. |
| publish_pathA | Publish a local file, a zip, or a whole directory to a public URL, preserving the directory structure. Use this when the page needs sibling files (CSS, JS, images) — write them into a directory first, then publish that directory. It is also the way to share any document: 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 instead of downloading a file. (PowerPoint files publish and download fine but have no rendered preview.) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have distinct intended use cases—single HTML pages versus files/directories with assets—but a simple standalone HTML file could reasonably be published with either, creating mild ambiguity. The descriptions help, but the boundary is not fully crisp.
Both tools follow a clear, consistent verb_noun snake_case pattern: publish_html and publish_path. This makes the naming predictable and easy to extend.
Two tools is on the thin side for a publishing service, but the pair covers the two main modes (single page vs. full path). It feels minimal but not unreasonable.
The tools cover publishing HTML and arbitrary paths, but there is no obvious way to manage, update, or unpublish previously published pages despite mentions of tokens and permanent storage. Basic publishing is covered, but lifecycle operations are missing.