MCP CamStream Analyzer

Created By
l1b0ka year ago
mcp server
Overview

what is MCP CamStream Analyzer?

MCP CamStream Analyzer is a tool for collecting and analyzing content from cameras and RTSP video streams, integrating with OpenAI-compatible APIs for detailed content analysis.

how to use MCP CamStream Analyzer?

To use MCP CamStream Analyzer, clone the repository, install dependencies, configure the config.yaml file, and run the service using Python.

key features of MCP CamStream Analyzer?

  • Image Analysis: Generate descriptions based on templates by providing image files.
  • Video Analysis: Supports frame-by-frame analysis or entire video analysis.
  • Multi-Camera Support: Works with system default cameras, external USB cameras, and RTSP stream cameras.

use cases of MCP CamStream Analyzer?

  1. Analyzing security footage for abnormalities.
  2. Generating descriptions of scenes from images.
  3. Monitoring live video streams for specific events.

FAQ from MCP CamStream Analyzer?

  • Can MCP CamStream Analyzer analyze any type of video stream?

Yes! It supports RTSP streams and various camera types.

  • Is there a configuration file required?

Yes! The config.yaml file is generated on the first run and needs to be configured with the API key and camera settings.

  • What programming language is used for MCP CamStream Analyzer?

The project is developed in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
l1b0k
Star
0
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
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
Crevio

2 days ago