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_pageA | Publish content you have in hand to a public URL. Use this whenever the user asks to share, send, publish, or "give me a link to" something you just produced — an HTML page (dashboard, report, chart, interactive page), a Markdown document, CSV, JSON, or a code/data file. Everything it publishes becomes a page the recipient opens in a browser: the filename decides how it renders, so pass "report.md" for Markdown instead of renaming it to .html. 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 tools share a common purpose of publishing to public URLs, but their descriptions clearly distinguish between publishing content already in hand (publish_page) and publishing local paths or directories (publish_path). The use cases are well delineated, though an agent might need to carefully read the descriptions to avoid misselection when sharing a file from disk.
Both tools follow the same verb_noun snake_case convention (publish_page, publish_path), making the pattern immediately predictable. The naming is perfectly consistent.
With only two tools, the server is on the lean side, but for its narrow scope of publishing content, each tool serves a distinct and necessary role. The count feels appropriate rather than insufficient.
The two tools cover the core publishing scenarios: inline content and file/directory paths. While there is no explicit update or delete mechanism, the descriptions mention in-place updates via token, so the surface is reasonably complete for the stated purpose.