Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PLOPINO_TOKENNoOptional. Publishes to your account: private boards, in-place updates, no per-IP rate limit. Create one at plopino.com/b
PLOPINO_BASE_URLNoBase 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation4/5

The split is clear in principle: publish_page takes in-hand content, publish_path takes a local file or directory. However, the descriptions overlap substantially — both claim to handle HTML, Markdown, code, and data files — which could make an agent hesitate over which to pick when content already exists as a local file.

Naming Consistency5/5

Both tools follow the same verb_noun pattern (publish_page, publish_path) with a shared prefix that signals a common action family. Fully predictable and readable.

Tool Count4/5

Two tools is on the thin side, but the server has a narrow, well-defined purpose (publishing artifacts to a public URL), and each tool covers a genuinely different input shape. Neither feels redundant.

Completeness3/5

The surface covers publishing but stops there: no update, list, or delete/unpublish operation, despite descriptions mentioning that token-backed pages can be updated in place and storage managed. An agent that wants to refresh or revoke a link has no tool for it.

Maintenance

ActivityNo data
ResponsivenessOutdated data