mcp-sse-server-demo

Created By
arthur-vra year ago
mcp sse server demo
Overview

what is mcp-sse-server-demo?

The mcp-sse-server-demo is a demonstration project for a server that utilizes Server-Sent Events (SSE) to push real-time updates to clients.

how to use mcp-sse-server-demo?

To use the mcp-sse-server-demo, clone the repository from GitHub, install the necessary dependencies, and run the server using the provided scripts. The default port is set to localhost:8083.

key features of mcp-sse-server-demo?

  • Real-time data streaming to clients using SSE.
  • Simple setup with TypeScript.
  • Built-in scripts for building and running the server.

use cases of mcp-sse-server-demo?

  1. Streaming live updates for notifications or alerts.
  2. Providing real-time data feeds for dashboards.
  3. Implementing live chat features in applications.

FAQ from mcp-sse-server-demo?

  • What is Server-Sent Events (SSE)?

SSE is a technology that allows a server to push real-time updates to web clients over HTTP.

  • How do I run the server?

You can run the server by executing the command npm start after building the project.

  • Is this project suitable for production use?

This is a demo project and may require further enhancements for production use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
arthur-vr
Star
0
Language
TypeScript
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)

2 days ago
Voyei

4 hours ago