@drop2run/mcp 0.12.0 → 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +30 -3
- package/dist/index.js +1157 -1037
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,11 +1,32 @@
|
|
|
1
1
|
# @drop2run/mcp
|
|
2
2
|
|
|
3
|
-
An MCP server that lets any MCP client — Claude, Cursor, VS Code, Codex, Gemini CLI — publish what it made to
|
|
3
|
+
An MCP server that lets any MCP client — Claude, ChatGPT, Cursor, VS Code, Codex, Gemini CLI — publish what it made to
|
|
4
4
|
[Drop2Run](https://dropto.run): an HTML page, a markdown note, a folder of documents or a built site. It
|
|
5
5
|
returns a live HTTPS URL.
|
|
6
6
|
|
|
7
7
|
Full documentation at [dropto.run/docs/mcp](https://dropto.run/docs/mcp).
|
|
8
8
|
|
|
9
|
+
## In a chat on the web — no package at all
|
|
10
|
+
|
|
11
|
+
Claude on the web and on a phone, ChatGPT and other hosted chats cannot run this package, so the same
|
|
12
|
+
tools are hosted at a URL:
|
|
13
|
+
|
|
14
|
+
```
|
|
15
|
+
https://mcp.dropto.run/mcp
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
**Claude** — connect it from
|
|
19
|
+
[Claude's connector directory](https://claude.ai/directory/connectors/drop2run) and sign in to Drop2Run
|
|
20
|
+
when asked. To add it by URL instead, open
|
|
21
|
+
[this link](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Drop2Run&connectorUrl=https%3A%2F%2Fmcp.dropto.run%2Fmcp)
|
|
22
|
+
or *Settings → Connectors → Add custom connector* and paste the URL.
|
|
23
|
+
**Claude Code** — `claude mcp add --transport http drop2run https://mcp.dropto.run/mcp`. **ChatGPT** — add
|
|
24
|
+
it as a custom connector, where your plan offers developer mode.
|
|
25
|
+
|
|
26
|
+
The hosted server has no `login` / `login_code` (the chat signs in for it) and no `publish_dir` (there is
|
|
27
|
+
no disk), and `publish_files` takes text files only. For a folder on disk, a PDF or an image, run the
|
|
28
|
+
package below.
|
|
29
|
+
|
|
9
30
|
## Setup
|
|
10
31
|
|
|
11
32
|
**Claude Desktop** — download [`drop2run.mcpb`](https://dropto.run/drop2run.mcpb) and open it. Claude
|
|
@@ -87,6 +108,7 @@ lose it.
|
|
|
87
108
|
| `list_sites` | Lists the sites on the account |
|
|
88
109
|
| `list_folders` | Lists the account's folders, each with the path `folder` accepts |
|
|
89
110
|
| `delete_site` | Deletes a site permanently, subdomain included — requires the subdomain repeated as `confirm` |
|
|
111
|
+
| `change_subdomain` | Moves a site to a new subdomain; the old one keeps redirecting — requires the current subdomain as `confirm` |
|
|
90
112
|
| `get_site` | Reads a site's settings, whether it is paused, and its versions with the live one marked |
|
|
91
113
|
| `update_site` | Changes a site's name, serving mode, password, invite-only, comments, forms, scheduled takedown or folder |
|
|
92
114
|
| `list_people` | Lists who a site is shared with, what each may do, and whether only they can open it |
|
|
@@ -104,8 +126,8 @@ Both publish tools take an optional `site` — a subdomain or site id to publish
|
|
|
104
126
|
new site is created.
|
|
105
127
|
|
|
106
128
|
Both also take an optional `subdomain`, which names the new site instead of letting the server generate
|
|
107
|
-
one. It is for a person who asked for a particular address: the name becomes the URL,
|
|
108
|
-
|
|
129
|
+
one. It is for a person who asked for a particular address: the name becomes the URL, and a site made
|
|
130
|
+
under a guessed one has to be deleted, or moved with `change_subdomain`, by hand. `site` and `subdomain` are
|
|
109
131
|
opposites — one publishes over a site that exists, the other creates one that does not — so passing both
|
|
110
132
|
is refused rather than resolved.
|
|
111
133
|
|
|
@@ -114,6 +136,11 @@ by path such as `Clients/Acme`, or by the id `list_folders` shows. Like `subdoma
|
|
|
114
136
|
site, so it cannot be combined with `site`. It never creates a folder: one that does not exist is refused
|
|
115
137
|
with the list of those that do, and nothing is published.
|
|
116
138
|
|
|
139
|
+
`change_subdomain` moves a site to a new address. The old one keeps working by redirecting to the new
|
|
140
|
+
one, and nobody else can take it. Each site gets two changes, and a change back to an old name counts
|
|
141
|
+
too, so it asks for the current subdomain as `confirm`. Visitors who signed in to the site or typed its
|
|
142
|
+
password are asked again on the new address. `get_site` shows the changes left and the former names.
|
|
143
|
+
|
|
117
144
|
`update_site` changes only the settings it is given. An empty `name`, `password` or `expiresAt` clears
|
|
118
145
|
that setting, and `folder: "root"` moves the site back to the top level. A takedown pauses the site by
|
|
119
146
|
default; `expiryAction: "delete"` removes it instead, and asks for the subdomain as `confirm` the way
|