Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
作者提供的说明(英文原文)
Publishes what an AI made — a page, a markdown or PDF doc, or a whole site — to a live HTTPS link.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.dropto.run/mcp打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"drop2run": {
"command": "npx",
"args": [
"-y",
"@drop2run/mcp"
]
}
}
}在终端中运行这条命令
claude mcp add --transport http drop2run https://mcp.dropto.run/mcpclaude mcp add drop2run -- npx -y @drop2run/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"drop2run": {
"url": "https://mcp.dropto.run/mcp"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"drop2run": {
"command": "npx",
"args": [
"-y",
"@drop2run/mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"drop2run": {
"type": "http",
"url": "https://mcp.dropto.run/mcp"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"drop2run": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@drop2run/mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.dropto.run/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 dropto.run 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 254 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.4.0)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Agent-Native Google Calendar - manage events, sync, and public booking
Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Source for the two Drop2Run packages that run on your machine: the drop2run command line tool and the @drop2run/mcp server.
Both are installed globally and then handed a credential. This repository exists so you can read what you are giving that credential to.
npm i -g drop2run # https://www.npmjs.com/package/drop2run
npx @drop2run/mcp # https://www.npmjs.com/package/@drop2run/mcp
The command line tool signs in through a browser and publishes a folder:
drop2run login
drop2run deploy dist
login needs a browser on the same machine; drop2run login --device covers a remote shell, and CI uses a DROP2RUN_TOKEN from https://app.dropto.run/account/tokens. The other commands are init, ls, open, rollback, rm, token list, whoami and where, and --json on any of them prints machine-readable output.
The MCP server is registered with a client rather than run by hand. Claude for macOS and Windows installs it from a bundle — download drop2run.mcpb and open it, and there is no config file and nothing to install first. Claude Code takes one command:
claude mcp add drop2run -s user -- npx -y @drop2run/mcp
A chat that cannot run a package — Claude on the web or a phone, ChatGPT — adds the hosted copy of the same server by URL instead, https://mcp.dropto.run/mcp, and signs in to Drop2Run when it connects. In Claude it is also listed in the connector directory. Its tools come from packages/mcp here (src/remote.ts); the sign-in in front of them does not. It publishes text files only, and the setup is at dropto.run/docs/mcp.
It exposes twenty tools, in five groups:
| Group | Tools |
|---|---|
| Publish | publish_files, publish_dir — the second reads a folder on disk, so it is local only |
| Sites | list_sites, list_folders, get_site, update_site, pause_site, resume_site, rollback_site, change_subdomain, delete_site |
| Sharing | list_people, invite_people, remove_person |
| Comments | list_comments, reply_comment, resolve_comment, reopen_comment |
| Sign-in | login, login_code — local server only; the hosted copy signs in when it connects |
The publishes answer with structured fields beside the sentence, so a URL does not have to be read back out of prose. delete_site and change_subdomain ask for the site's current subdomain repeated back before they run; pause_site is the reversible way to take a site off the air. The token goes to the same place the CLI stores one, so signing in through either covers both.
Each package documents itself in full, including the sign-in flows and what happens without a site: packages/cli/README.md and packages/mcp/README.md. The hosted documentation is at dropto.run/docs/cli and dropto.run/docs/mcp.
| Package | Published | What it is |
|---|---|---|
packages/cli | drop2run | The command line tool: login, deploy, ls, rollback, rm |
packages/mcp | @drop2run/mcp | An MCP server, so an agent can publish what it just wrote |
packages/core | no | The deploy engine — manifest, hashing, upload, go-live. No Node APIs, no browser APIs |
packages/node | no | The parts that need fs: reading a folder, the config file, the token store |
core and node are not published. They are bundled into each package's dist/ at build time, which is why drop2run installs with no runtime dependencies at all — an intentional choice for something that holds a token. @drop2run/mcp has two, both required by the protocol: @modelcontextprotocol/sdk and zod.
Each package stands alone — there is no workspace root, and internal imports resolve through the relative paths in each tsconfig.json.
cd packages/cli # or mcp, or node
npm ci npm run typecheck npm test npm run build # writes dist/, which is what npm ships
packages/core has no dependencies and no build of its own; it is typechecked by the packages that bundle it.
This repository is an export of the four packages above, with their full history. The Drop2Run service itself — the API, the edge router, the dashboard — is not here and is not open source. What that means in practice: the code that decides what happens to a file after it leaves your machine is not something this repository lets you audit. What it does let you audit is everything that happens to your files and your token *before* that point, which is the part that runs with your privileges.
Issues about the CLI or the MCP server are welcome here. Anything about the hosted service belongs at dropto.run/contact.
Pull requests are welcome too, with one thing worth knowing first: this repository is generated, so a pull request is not merged here. The change is applied in the source repository and reaches this one in the next export, with your commit and its authorship carried along; the pull request is then closed with a link to the commit. Merging it here instead would put a commit in this history that no future export contains, and the two would diverge on the very next update.
MIT.