Node Server Orchestrator

io.github.ShingWongPublished by GitHub account ShingWongv1.0.0Updated Oct 24, 2026

MCP server for orchestrating Node.js development servers (backend, frontend, databases, etc.)

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an assistant orchestrate Node.js development servers, such as backend, frontend and database processes.

What you can do
Start, stop and coordinate Node.js development servers from an assistant session, covering backend, frontend and database processes as described in the registry entry. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Useful when a project runs several Node.js development servers and you want an assistant to manage those processes instead of switching between terminals by hand.
Requirements
Runs as a local process on the user's machine via the npm package node-server-orchestrator over stdio. Desktop client only; no web execution. No authentication, environment variables or headers are declared.
Before you install
It manages local development processes, so starting or stopping servers can interrupt running work or free ports unexpectedly. No tools, README or instructions are published, so review the package before installing.

Installation

In SourceWeft

  1. Open Node Server Orchestrator in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.