drop2run-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DROP2RUN_TOKEN | No | Access token. Not needed to start the server or list its tools; every tool call requires it. | |
| DROP2RUN_API_URL | No | API base URL. Defaults to the hosted service. |
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 |
|---|---|
| loginA | Signs in through a browser on this machine and stores an access token, which every other tool then uses. Opens the browser here and waits for the person to approve. If it answers that nothing has been approved yet, call it again to keep waiting — that is not a failure. Needs no command line and no token pasted by hand. |
| login_codeA | Signs in where no browser can be opened on this machine — a container, a remote host. The first call returns a short code and a URL to enter it at, which the person opens anywhere; call it again to wait for the approval and store the token. |
| publish_filesA | Publishes one or more files written here — markdown, HTML, CSS, JSON — as a site, and returns its URL. A single page goes at index.html; a single .md, .markdown or .pdf file is a site on its own, served through the documents viewer. Text only: a PDF or an image has to be published from disk with publish_dir. |
| publish_dirB | Publishes a folder of static files and returns its URL. The folder needs an index.html at its root, or .md and .pdf files, which are served through the reader. |
| delete_siteA | Takes a site down permanently — its files, its history and its subdomain. Nothing here undoes it, and the subdomain becomes available for anybody to claim. Requires |
| list_sitesA | Lists the sites on this account, so a publish can go to one of them. |
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 6 tools
login and login_code are clearly differentiated by environment (browser vs. headless), and publish_files vs publish_dir are distinguished by input type (files vs directory). However, the boundary between publishing text content and static files could be slightly clearer, as both result in a site.
All tool names use snake_case and follow a verb_noun or noun_verb pattern (login_code, publish_files, delete_site, list_sites). The only minor deviation is 'login' lacking a noun, but it's intuitive and consistent overall.
Six tools provide a well-scoped set covering authentication, publishing, deletion, and listing. Each tool earns its place without redundancy or excessive granularity.
The surface covers authentication, publishing, listing, and deletion, which are the core operations for managing sites. Minor gaps include no explicit update or rename for existing sites, and no tool to retrieve a site's metadata or content, but these are workaroundable by re-publishing or listing.