NitroStack Logo
/cli
/start

Start Command

Overview

The start command launches your built NitroStack MCP server in production mode. Unlike the dev command, it executes the compiled code without file watchers or development proxies, providing maximum throughput and low latency.

Usage

Bash
npx @nitrostack/cli start [options]
# or via npm script in a scaffolded project:
npm run start

[!NOTE] Ensure you have run npm run build (or npx @nitrostack/cli build) before starting the server so the production bundle in dist/ is up to date.

Options

OptionDescriptionDefault
--port <port>Port for the HTTP / SSE server3000

Examples

1. Default Port

Start the server listening on port 3000:

Bash
nitrostack-cli start

2. Custom Port

Start the server on a custom port (e.g. for cloud deployments or containers):

Bash
nitrostack-cli start --port 8080

Transport Endpoints in Production

When starting over HTTP (or dual transport), NitroStack exposes two endpoints on the configured port:

  1. Streamable HTTP: http://localhost:<PORT>/mcp
    • Primary endpoint for JSON-RPC 2.0 requests (tools/call, resources/read, server/discover).
  2. Legacy SSE: http://localhost:<PORT>/sse
    • SSE connection endpoint for clients that require the classic Server-Sent Events handshake (e.g. Cursor IDE, legacy MCP clients).

Next Steps

Documentation Home•View All Docs•GitHub