The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Netrun listing page.
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
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
~/.cursor/mcp.json.claude mcp add netrun -s user -e NETRUN_API_KEY=nru_… -- npx -y netrun-mcpcodex mcp add netrun --env NETRUN_API_KEY=nru_… -- npx -y netrun-mcpNode.js has to be installed — AI editors usually ship with it.
| 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 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_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. |
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).
io.github.fadeynotchenko/netrunMIT