Skip to main content
Glama
fadeynotchenko

netrun-mcp

by fadeynotchenko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to netrun-mcp

No user-submitted related servers found.

    Related Servers

    • pocketnook

      shotintoeternity
      A
      license
      Not graded
      quality
      B
      maintenance
      Deploy GitHub repositories or local directories to private URLs directly from an MCP client. Includes tools for managing deployments, reading build logs, and stopping services.
      24 npm
      MIT

    • sitedrop

      t0saki
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for self-hosted static site publishing on Cloudflare Workers. Enables AI coding agents to deploy pages with a single 'publish' tool and get live URLs, with support for atomic updates, versioning, and per-site passwords.
      3 npm
      MIT

    • localmcpcoder

      JuanseGZZ
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables remote MCP clients like ChatGPT to run shell commands and manage files on your local machine via a Cloudflare tunnel, exposing tools for file operations, search, and task management.
      3
      MIT

    • WeInc

      umairalisadaqat
      F
      license
      Not graded
      quality
      C
      maintenance
      Hosted remote MCP server for WeInc (we.inc), the AI website builder. Manage projects, publishing, custom domains, and previews from Claude, Cursor, or any MCP client - nothing to install.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources