netrun_whoami
Netrun account
The plan, how many projects are available and how much free running time bots have left.
Takes no parameters.
Netrun
io.netrunPublished by netrun.ioOfficial publisherv0.4.0Updated Oct 30, 2026
Publish websites and Telegram bots to Netrun — upload a folder from your editor, get a URL
VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper ToolsCommunication & Collaboration
Overview
AI-generated overview
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.
- What you can do
- Publish and update projects: upload a folder, auto-detect the stack, wait for the build and get the URL or failure reason
- Inspect projects: list all projects with URLs and state, check plan, project quota and remaining free running time
- Diagnose: read status (blocking issues, saved secret names, last failure) and the last lines of application logs
- Manage secrets: save tokens and API keys as encrypted environment variables and re-publish
- Domains and links: return DNS records for a custom domain, verify them, and request a public HTTPS address
- Control: start, stop or restart a project
- When to use it
- Useful when you want an assistant to put a small website, API or chat bot online without managing a server, and to check why a deployed app is silent or failing. Also handy for updating an existing project after a code change.
- Requirements
- Remote option: Streamable HTTP endpoint with OAuth sign-in by email, no key needed (custom connectors in ChatGPT need a paid plan and developer mode). Local option: Node.js and the npm package run via npx, with the NETRUN_API_KEY environment variable (a personal access key created on the Netrun MCP page). A Netrun account is required; custom domains need a paid plan.
Before you install
The assistant uploads your project folder to Netrun's servers, so review what the folder contains. Secrets you provide are stored encrypted and write-only, but they are sent through the assistant. Publishing, restarting and changing secrets change live state; builds take minutes and repeated publishes should be avoided. The agent cannot pay, renew plans or delete projects, and custom domains require a paid plan. Free-plan bots stop after limited running time.
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.netrun%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.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:
- 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
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
9netrun_list_projects
List Netrun projects
All projects of the account with URLs and state.
Takes no parameters.
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.
Parameters
project_idrequirednetrun_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.
Parameters
linesproject_idrequirednetrun_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.
Parameters
namepathrequiredwaitcommentsecretsproject_idskip_secretswait_secondsnetrun_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.
Parameters
filepublishsecretsrequiredproject_idrequirednetrun_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.
Parameters
actiondomainproject_idrequirednetrun_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).
Parameters
waitneededrequiredproject_idrequiredwait_secondsnetrun_control
Start / stop / restart
Start, stop or restart a project. On the Free plan a bot’s free running time is counted only while it runs.
Parameters
actionrequiredproject_idrequiredVersion history
1- v0.4.0LatestOct 29, 2026
Score
100% 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
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
