Simple MCP Streamable HTTP Server

Created By
hydroweavera year ago
Simple MCP Streamable HTTP Server with Express based on Anthropic Example
Overview

what is Simple MCP Streamable HTTP Server?

Simple MCP Streamable HTTP Server is a lightweight server built on Express that allows for streaming HTTP communication based on the Model Context Protocol (MCP).

how to use Simple MCP Streamable HTTP Server?

To use the server, clone the repository, install the dependencies, build the project, and start the server. You can then expose it via ngrok and use the provided URL with the MCP inspector.

key features of Simple MCP Streamable HTTP Server?

  • Built on Express for easy setup and configuration
  • Supports streaming HTTP communication
  • Easy integration with ngrok for public access

use cases of Simple MCP Streamable HTTP Server?

  1. Streaming data to clients in real-time.
  2. Integrating with applications that require MCP for communication.
  3. Testing and developing applications that utilize streaming HTTP.

FAQ from Simple MCP Streamable HTTP Server?

  • What is MCP?

MCP stands for Model Context Protocol, which is used for streaming data.

  • How do I expose the server to the internet?

You can use ngrok to expose your local server to the internet easily.

  • Is this server suitable for production use?

This server is designed for development and testing purposes; for production, consider additional security and performance optimizations.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hydroweaver
Star
0
Language
JavaScript
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