Netrun

io.github.fadeynotchenkoPublished by GitHub account fadeynotchenkov0.3.1Updated Oct 27, 2026

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

The publisher's own server: Netrun

VerifiedStreamable HTTPWeb executableCloud & Infrastructure Developer Tools Communication & Collaboration

Server details

Identifier: io.github.fadeynotchenko/netrun
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 22, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account fadeynotchenko for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

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

Overview

AI-generated overview

Netrun lets an assistant publish a code folder as a hosted website or Telegram bot, then check status, logs, secrets, domains and restarts.

What you can do: Publish a project folder as a new project or new version, with stack detection, build waiting and a returned URL or failure reason
Check a project's running state, URL, blockers, configured secrets and last publish failure
Read the last lines of application output
Save tokens and API keys as encrypted environment variables and re-publish
Enable a public HTTPS address and point a custom domain at the site, checking registrar records
Start, stop or restart projects, list all account projects, and show plan and remaining free running time
When to use it: Useful when you build small sites or Telegram bots in an AI editor and want the assistant to deploy them and hand back a link without leaving the chat. Also handy for quick operational checks such as why a bot went silent or whether a domain is live.
Requirements: Either the remote endpoint with OAuth sign-in by email, or the local npm package netrun-mcp run with Node.js. The local route needs a Netrun account and a personal access key in NETRUN_API_KEY, plus network access to the Netrun API. Custom connections in ChatGPT require a paid plan and developer mode.

Before you install

The access key is a credential stored in the editor config; revoke it in the dashboard if exposed. Publishing uploads your code folder to Netrun, and secrets you save are sent to and stored by that service. The agent can start, stop, restart and re-publish projects, which changes live deployments; it cannot pay, renew plans or delete projects.

Installation

In SourceWeft

Open Netrun in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.fadeynotchenko%2Fnetrun/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "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

Source: README.md at commit 2581702

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v0.3.1LatestOct 12, 2026
v0.3.0Oct 6, 2026
v0.1.0Sep 22, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Other Netrun integrations

Netrun

io.netrunOfficial publisher

Netrun deploys websites and bots (Telegram, Discord) from your editor: an assistant uploads a project folder, waits for the build and returns a public URL.

Streamable HTTPWeb executableAuth

Cloud & Infrastructure9 toolsOct 30, 2026