Publish websites and Telegram bots to Netrun — upload a folder from your editor, get a URL
One address for any MCP client. You sign in at api.netrun.io once, after adding it.
At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
| Access to | Read | Change |
|---|---|---|
| Netrun | Not stated: netrun:projects | |
From the sign-in at api.netrun.io, as the endpoint publishes it. You approve it there.
Odel could not list its tools without signing in.
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
{
"mcpServers": {
"netrun": {
"command": "npx",
"args": ["-y", "netrun-mcp@latest"],
"env": {
"NETRUN_API_KEY": "nru_…"
}
}
}
}
~/.cursor/mcp.json.claude mcp add netrun -s user -e NETRUN_API_KEY=nru_… -- npx -y netrun-mcp@latestcodex mcp add netrun --env NETRUN_API_KEY=nru_… -- npx -y netrun-mcp@latestNode.js has to be installed — AI editors usually ship with it.
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.
| 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. |
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