Lps Mcp Server

Created By
Aodian Cloud9 months ago
Overview

what is Lps Mcp Server?

Lps Mcp Server is a service based on the LPS (Live Streaming Distribution System) that provides management capabilities for live streaming, including pushing, pulling, and distributing streams, as well as obtaining live quality data.

how to use Lps Mcp Server?

To use Lps Mcp Server, install it via npm with the command npm install lps-mcp-server, and then run it using npm run start or node app_stdio.js after setting the required environment variables.

key features of Lps Mcp Server?

  • Supports multiple streaming protocols including RTMP, SRT, HLS, FLV, and WEBRTC.
  • Provides tools for managing live stream projects and distribution.
  • Offers data analysis tools for monitoring stream quality.

use cases of Lps Mcp Server?

  1. Managing live streaming projects for events.
  2. Distributing streams to various platforms simultaneously.
  3. Analyzing stream quality metrics for performance improvement.

FAQ from Lps Mcp Server?

  • What protocols does Lps Mcp Server support?

Lps Mcp Server supports RTMP, SRT, HLS, FLV, and WEBRTC protocols.

  • How do I set up the environment variables?

You need to set ACCESS_ID and ACCESS_KEY as environment variables before starting the server.

  • Can I run Lps Mcp Server locally?

Yes, you can run it locally by following the installation and startup instructions.

Server Config

{
  "mcpServers": {
    "lps-mcp-server": {
      "args": [
        "-y",
        "lps-mcp-server@latest"
      ],
      "command": "npx",
      "env": {
        "ACCESS_ID": "<YOUR_ACCESS_ID>",
        "ACCESS_KEY": "<YOUR_ACCESS_KEY>",
        "MLPS_URL": "<MLPS_API_URL>"
      }
    }
  }
}
Project Info
Created At
9 months ago
Updated At
8 months ago
Author Name
Aodian Cloud
Star
-
Language
-
License
-
Tags

Recommend Servers

View All
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago