Netrun

io.netrun由 netrun.io 發布官方發布者v0.4.0更新於 Oct 30, 2026

Publish websites and Telegram bots to Netrun — upload a folder from your editor, get a URL

已驗證Streamable HTTP可網頁執行雲端與基礎設施開發者工具溝通與協作

服務詳細資訊

識別碼: io.netrun/netrun
傳輸: Streamable HTTP
執行環境: Web executable
信任: Verified
發布於: Oct 29, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此服務的命名空間屬於 netrun.io，且該網域同時執行其端點。這可以確認發布者，但並不代表該服務的工具是安全的。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.netrun%2Fnetrun.svg)](https://sourceweft.com/mcp/io.netrun%2Fnetrun?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

Netrun 讓助理從編輯器部署網站與機器人（Telegram、Discord）：上傳專案資料夾、等待建置並回傳公開網址。

可以做什麼: 發布與更新專案：上傳資料夾、自動辨識技術堆疊、等待建置並回傳網址或失敗原因
檢視專案：列出帳號下所有專案及其網址與狀態，查看方案、專案額度與剩餘免費執行時間
排查問題：讀取狀態（阻塞原因、已儲存的密鑰名稱、上次發布失敗原因）與應用程式日誌最後幾行
管理密鑰：將權杖與 API 金鑰存成加密的環境變數並重新發布
網域與連結：回傳自訂網域需新增的 DNS 記錄、驗證記錄，並為專案申請公開 HTTPS 位址
控制執行：啟動、停止或重新啟動專案
適用情境: 適合想讓助理把小型網站、API 或聊天機器人上線、又不想自行管理伺服器的情況，也適合排查已部署應用為何沒有回應或失敗。程式碼修改後更新既有專案時同樣方便。
執行需求: 遠端方式：Streamable HTTP 端點，以電子郵件 OAuth 登入，不需金鑰（ChatGPT 自訂連接需付費方案並開啟開發者模式）。本機方式：需安裝 Node.js，透過 npx 執行 npm 套件，並設定環境變數 NETRUN_API_KEY（在 Netrun 的 MCP 頁面建立的個人存取金鑰）。需要 Netrun 帳號；自訂網域需付費方案。

安裝前請注意

助理會把專案資料夾上傳到 Netrun 的伺服器，請先確認資料夾內容。提供的密鑰會加密儲存且僅可寫入，但仍會經由助理傳遞。發布、重新啟動與變更密鑰會改變線上狀態；建置需數分鐘，應避免反覆發布。助理無法付款、續訂方案或刪除專案，自訂網域需付費方案。免費方案的機器人在執行時間用盡後會停止。

安裝

在 SourceWeft 中

開啟儀表板中的 Netrun，將其新增到工作區。
連接所需的憑證。它們會被私密儲存，絕不會在公開頁面上展示。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.netrun%2Fnetrun/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "netrun": {
      "type": "http",
      "url": "https://api.netrun.io/v1/mcp"
    }
  }
}

README

netrun-mcp

Publish websites and Telegram bots to Netrun — upload a folder from your editor, get a URL.

Connect Netrun to your AI editor and just ask: “publish this bot”. The agent uploads your code folder and sends back the link. MCP is the common way to connect external services to AI editors. With Netrun connected, you tell the agent in chat that you want the project online: it uploads the code folder, asks for a token if the code needs one, waits for the build and gives you the link. Works in Cursor, Claude Code, Codex, Claude Desktop, VS Code and Windsurf, and in ChatGPT and Claude right in the browser.

Publish this bot to Netrun

I fixed the greeting — update the project

Why is the bot silent? Check the logs

Change the bot token and restart

Setup (one minute)

Sign in at netrun.io → MCP (https://netrun.io/mcp) → create an access key.
Connect your editor. The MCP page gives you a ready button or command with the key already inside; the generic form is:

json

{  "mcpServers": {    "netrun": {      "command": "npx",      "args": ["-y", "netrun-mcp@latest"],      "env": {        "NETRUN_API_KEY": "nru_…"      }    }  }}

{  "mcpServers": {    "netrun": {      "command": "npx",      "args": ["-y", "netrun-mcp@latest"],      "env": {        "NETRUN_API_KEY": "nru_…"      }    }  }}

Cursor — click Add to Cursor on the MCP page, or put the JSON above into ~/.cursor/mcp.json.
Claude Code — claude mcp add netrun -s user -e NETRUN_API_KEY=nru_… -- npx -y netrun-mcp@latest
Codex — codex mcp add netrun --env NETRUN_API_KEY=nru_… -- npx -y netrun-mcp@latest
Claude Desktop, VS Code, Windsurf — the JSON above in the MCP servers config.

Node.js has to be installed — AI editors usually ship with it.

ChatGPT, Claude in the browser — no install, no key

Netrun also runs as a remote MCP server: https://api.netrun.io/v1/mcp (Streamable HTTP, OAuth sign-in). In the chat settings open connections (Connectors or Apps), add a custom one with this address and press Connect. You sign in to Netrun by email — no key needed. ChatGPT allows custom connections on paid plans — turn on developer mode in the settings. Claude allows them on every plan, one on the free plan. The agent takes the code right from the conversation; a large multi-file project is easier to publish from an editor.

What the agent can do

Tool	What it does
`netrun_publish`	Uploads a project folder and puts it online — a new project or a new version of an existing one. Detects the stack (Python, Node, Go, Rust, PHP, static HTML, Docker, docker-compose), asks for missing secrets, waits for the build and returns the URL or the failure reason.
`netrun_status`	Is the project running, its URL, what blocks it, which secrets are already set and why the last publish failed.
`netrun_logs`	Last lines of the application output — the first place to look when a bot goes silent.
`netrun_set_secrets`	Saves tokens and API keys as environment variables (stored encrypted) and re-publishes so the app picks them up.
`netrun_link`	Decides whether the project gets a public HTTPS address — for example a webhook bot we took for a background program. Re-publishes the project; the link appears if the app answers requests from the internet.
`netrun_domains`	Points your own domain at the site and checks whether the registrar settings have taken effect. Until they have, it shows which records to add.
`netrun_control`	Start, stop or restart a project.
`netrun_list_projects`	All projects of the account with URLs and state.
`netrun_whoami`	The plan, how many projects are available and how much free running time bots have left.

What it deliberately cannot do

The agent cannot pay, renew a plan or buy places — you do that in the dashboard.
It cannot delete projects or files from persistent storage either — anything irreversible stays with you.
If the code needs a token or a password, the agent asks you before publishing — it never makes values up.
The access key lives only in your editor config, and a connected chat is listed in the dashboard — you can revoke either there at any time.

How it works

This package is a thin courier: it zips the folder (honouring .gitignore), sends it to the Netrun API with your key, and asks for status and logs. Building, running, HTTPS and addresses all happen on Netrun.

Environment variables: NETRUN_API_KEY (required), NETRUN_API_URL (default https://api.netrun.io/v1), NETRUN_APP_URL (default https://netrun.io).

Registry: io.netrun/netrun
Source: https://github.com/netrun-io/netrun-mcp

MIT

來源：README.md，提交 2581702

工具

netrun_whoami

Netrun account

The plan, how many projects are available and how much free running time bots have left.

無需輸入參數。

netrun_list_projects

List Netrun projects

All projects of the account with URLs and state.

無需輸入參數。

netrun_status

Project status

Is the project running, its URL, what blocks it, which secrets are already set and why the last publish failed. It also lists the names of the secrets already saved; their values are never returned.

輸入參數project_id必填

netrun_logs

Project logs

Last lines of the application output — the first place to look when a bot goes silent. Most failures name their cause in the last lines.

輸入參數linesproject_id必填

netrun_publish

Publish to Netrun

Uploads a project folder and puts it online — a new project or a new version of an existing one. Detects the stack (Python, Node, Go, Rust, PHP, static HTML, Docker, docker-compose), asks for missing secrets, waits for the build and returns the URL or the failure reason. A new project takes a name; an existing one is updated by project_id. When the code needs secrets that are not set yet, the result is needs_secrets with their names, and values go in “secrets”. A build takes 1-5 minutes.

輸入參數namepath必填waitcommentsecretsproject_idskip_secretswait_seconds

netrun_set_secrets

Set project secrets

Saves tokens and API keys as environment variables (stored encrypted) and re-publishes so the app picks them up. Values are write-only and are never returned.

輸入參數filepublishsecrets必填project_id必填

netrun_domains

Custom domain

Points your own domain at the site and checks whether the registrar settings have taken effect. Until they have, it shows which records to add. The result lists the DNS records to add at the registrar; action "check" verifies them. Records take minutes to hours to spread. Custom domains need a paid plan and a website (bots have no address). Removing a domain is only available in the dashboard.

輸入參數actiondomainproject_id必填

netrun_link

Public link

Decides whether the project gets a public HTTPS address — for example a webhook bot we took for a background program. Re-publishes the project; the link appears if the app answers requests from the internet. Netrun guesses from the code whether a project needs an address, and a webhook bot or an API can look like a background program. needed=true gives the project a URL, needed=false removes it; the choice survives later code updates. The project is re-published (a short restart). The link appears only if the app listens on 0.0.0.0 on the port from the PORT environment variable; otherwise the project keeps running in the background without a link. The URL is not registered with the bot platform automatically (for Telegram that is setWebhook).

輸入參數waitneeded必填project_id必填wait_seconds