Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@sigma-streaming-platform-mcpFind apps with error channels"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
A Personal API Token — create at your Sigma portal under Settings → API Tokens
Node.js 22+
Related MCP server: Railway MCP Server
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-fixDeployment Options
This MCP supports two deployment paths without changing the server architecture:
npxfor direct local executionDocker for a containerized stdio process launched via
docker run -i --rm sigmastreaming/cloud-mcp
Choose Docker when your MCP client can invoke Docker directly and you want isolated runtime dependencies.
Run Via npx
The package currently published on npm is @sigmaott/cloud-mcp. Run the MCP server directly with:
SIGMA_TOKEN=pat_your_token_here \
SIGMA_BASE_URL=https://api.sigma.example.com \
npx -y @sigmaott/cloud-mcpThis 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 sigmastreaming/cloud-mcp .Or use the bundled script:
npm run docker:buildRun 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 \
sigmastreaming/cloud-mcp:latestOr, 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:runEnvironment Variables
Variable | Required | Description |
| ✅ | Personal API Token ( |
| ✅ | Traefik ingress URL (e.g. |
Claude Desktop Configuration
Using npx
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"sigma-streaming-platform": {
"command": "npx",
"args": ["-y", "@sigmaott/cloud-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",
"sigmastreaming/cloud-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", "@sigmaott/cloud-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",
"sigmastreaming/cloud-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 traefikThen use:
SIGMA_BASE_URL=http://localhost:8080Available Tools
Tool | Params | Description |
| page?, perPage?, search? | List all tenant apps/workspaces |
| appId | Get app detail |
| appId, page?, perPage? | List media servers for an app |
| appId, serverId | Get server detail |
| appId, status?, name?, page?, perPage? | List transcoding channels |
| appId, channelId | Get channel detail |
| appId | List channels in error state |
| appId, channelId | Start a stopped channel |
| appId, channelId | Stop a 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
Create
src/services/sigma-<name>.service.tsCreate
src/tools/<name>/with tool handlersRegister in
src/tools/tool-registry.tsAdd service instance in
src/main.ts
Publish To npm
Use the published package name
@sigmaott/cloud-mcp.Run
npm login.Bump the version with
npm version patch(orminor/major).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 -iso stdin/stdout remain attached to the MCP client.Rebuild the image after changing source code or package dependencies.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/vietanha34/sigma-platform-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
