npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@sigmaott/cloud-mcp

v1.0.1

Published

Sigma Platform MCP server for DevOps operators

Readme

sigma-streaming-platform-mcp

MCP server for Sigma Streaming Platform. Lets DevOps operators query and operate the platform from any AI client (Claude Desktop, Cursor, Kiro).

Prerequisites

  1. A Personal API Token — create at your Sigma portal under Settings → API Tokens
  2. Node.js 22+

Setup

cd /path/to/sigma-streaming-platform-mcp
npm install
npm run build    # uses tsgo (TypeScript native compiler)
npm run lint     # uses Biome for linting + formatting
npm run lint:fix # auto-fix

Deployment Options

This MCP supports two deployment paths without changing the server architecture:

  1. npx for direct local execution
  2. Docker for a containerized stdio process launched via docker run -i --rm ...

Choose Docker when your MCP client can invoke Docker directly and you want isolated runtime dependencies.

Run Via npx

After publishing to npm, you can run the MCP server directly with:

SIGMA_TOKEN=pat_your_token_here \
SIGMA_BASE_URL=https://api.sigma.example.com \
npx -y sigma-streaming-platform-mcp

This works because the package exposes a CLI binary pointing to dist/main.js.

Run Via Docker

Build the image from this repository:

docker build -t sigma-streaming-platform-mcp .

Or use the bundled script:

npm run docker:build

Run the MCP server as a stdio container:

docker run -i --rm \
  -e SIGMA_TOKEN=pat_your_token_here \
  -e SIGMA_BASE_URL=https://api.sigma.example.com \
  sigma-streaming-platform-mcp:latest

Or, if you prefer to pass environment variables from your current shell:

export SIGMA_TOKEN=pat_your_token_here
export SIGMA_BASE_URL=https://api.sigma.example.com
npm run docker:run

Environment Variables

| Variable | Required | Description | |----------|----------|-------------| | SIGMA_TOKEN | ✅ | Personal API Token (pat_...) | | SIGMA_BASE_URL | ✅ | Traefik ingress URL (e.g. https://api.sigma.example.com) |

Claude Desktop Configuration

Using npx

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "sigma-streaming-platform": {
      "command": "npx",
      "args": ["-y", "sigma-streaming-platform-mcp"],
      "env": {
        "SIGMA_TOKEN": "pat_your_token_here",
        "SIGMA_BASE_URL": "https://api.sigma.example.com"
      }
    }
  }
}

Using Docker

If Claude Desktop on your machine can invoke Docker directly, use:

{
  "mcpServers": {
    "sigma-streaming-platform": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "SIGMA_TOKEN",
        "-e",
        "SIGMA_BASE_URL",
        "sigma-streaming-platform-mcp:latest"
      ],
      "env": {
        "SIGMA_TOKEN": "pat_your_token_here",
        "SIGMA_BASE_URL": "https://api.sigma.example.com"
      }
    }
  }
}

Kiro CLI Configuration

Using npx

Add to ~/.kiro/settings/mcp.json:

{
  "mcpServers": {
    "sigma-streaming-platform": {
      "command": "npx",
      "args": ["-y", "sigma-streaming-platform-mcp"],
      "env": {
        "SIGMA_TOKEN": "pat_your_token_here",
        "SIGMA_BASE_URL": "https://api.sigma.example.com"
      }
    }
  }
}

Using Docker

{
  "mcpServers": {
    "sigma-streaming-platform": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "SIGMA_TOKEN",
        "-e",
        "SIGMA_BASE_URL",
        "sigma-streaming-platform-mcp:latest"
      ],
      "env": {
        "SIGMA_TOKEN": "pat_your_token_here",
        "SIGMA_BASE_URL": "https://api.sigma.example.com"
      }
    }
  }
}

Local Development (kubectl port-forward)

If accessing via port-forward to the Traefik ingress:

kubectl port-forward svc/traefik 8080:80 -n traefik

Then use:

SIGMA_BASE_URL=http://localhost:8080

Available Tools

| Tool | Params | Description | |------|--------|-------------| | list_apps | page?, perPage?, search? | List all tenant apps/workspaces | | get_app_detail | appId | Get app detail | | list_servers | appId, page?, perPage? | List media servers for an app | | get_server_info | appId, serverId | Get server detail | | list_channels | appId, status?, name?, page?, perPage? | List transcoding channels | | get_channel_detail | appId, channelId | Get channel detail | | list_error_channels | appId | List channels in error state | | start_channel | appId, channelId | Start a stopped channel | | stop_channel | appId, channelId | Stop a channel | | restart_channel | appId, channelId | Restart a channel (error recovery) |

Typical Workflow

User: "Tìm xem app nào đang có channel lỗi"

AI → list_apps()
   → [{id: "app_abc", name: "VTV Live"}, ...]

AI → list_error_channels(appId: "app_abc")
   → [{channelId: "ch_1", name: "VTV HD", status: "error"}]

AI → restart_channel(appId: "app_abc", channelId: "ch_1")
   → {success: true}

Adding More Services

  1. Create src/services/sigma-<name>.service.ts
  2. Create src/tools/<name>/ with tool handlers
  3. Register in src/tools/tool-registry.ts
  4. Add service instance in src/main.ts

Publish To npm

  1. Ensure the package name sigma-streaming-platform-mcp is available on npm.
  2. Run npm login.
  3. Bump the version with npm version patch (or minor / major).
  4. Publish with npm publish.

Because prepack runs npm run build and files only includes dist plus README.md, the published tarball is ready for npx and excludes local workspace artifacts.

Docker Notes

  • This image keeps the MCP transport on stdio; it does not expose HTTP or SSE.
  • Use docker run -i so stdin/stdout remain attached to the MCP client.
  • Rebuild the image after changing source code or package dependencies.