netrun-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETRUN_API_KEY | Yes | Your Netrun API access key (required). Found on the Netrun MCP page. | |
| NETRUN_API_URL | No | Base URL for the Netrun API. | https://api.netrun.io/v1 |
| NETRUN_APP_URL | No | Base URL for the Netrun web app. | https://netrun.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| netrun_whoamiA | Who the configured key belongs to, the current plan, project limit and — on the Free plan — how much free running time bots have left. Call it first when the user asks anything about their Netrun account or limits. |
| netrun_list_projectsA | All projects of the account with id, kind, status and public URL. Use it to find project_id for other tools. |
| netrun_statusA | Current state of one project: is it running, its URL, what blocks it, and — if the last publish failed — why (stage, reason, stderr tail). |
| netrun_logsA | Last lines of the application output (stdout/stderr) — the first place to look when a bot is silent or a site errors. |
| netrun_publishA | Upload a project folder and put it online: creates a new project (pass name) or ships a new version of an existing one (pass project_id). Detects the language automatically (Python, Node, Go, Rust, PHP, static HTML, Docker, docker-compose…). Waits for the build and returns the public URL or the failure reason. If it returns needs_secrets, ask the user for the values and call again with "secrets". |
| netrun_set_secretsA | Save environment variables (tokens, API keys, passwords) for a project. Values are stored encrypted and never returned. By default the project is re-published so the app picks them up. Ask the user for the values — do not invent them. |
| netrun_controlB | Start, stop or restart a project. Stopping a Free-plan bot does not pause its free running time. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct aspect: account info, project listing, per-project status, logs, publishing, secrets, and control actions. There is no overlap in purpose, and descriptions clarify when to use each.
All tool names use snake_case with a clear 'netrun_' prefix, but the pattern is mixed: some are verbs (publish, control), some nouns (status, logs), and 'whoami' is a command. Still, names are intuitive and predictable, with minor deviation from a strict verb_noun convention.
Seven tools is well-scoped for a deployment platform sever. Each tool covers a necessary function without redundancy, and the count is within the ideal range.
The tool set covers the core lifecycle: account info, project discovery, status, logs, publish/update, secrets, and start/stop/restart. A delete project operation is absent, but this is a minor gap that does not break typical workflows.