HMR Docs

Created By
Muspi Merol9 months ago
Provide docs and source code access for the HMR library on PyPI. Docs: https://py3.online/hmr
Overview

what is HMR?

HMR (Hot Module Replacement) is a library that provides documentation and source code access for developers using Python. It allows for efficient development by enabling modules to be replaced without a full reload.

how to use HMR?

To use HMR, you can access the documentation at HMR Docs and utilize the library by running the command: npx mcp-remote https://pyth-on-line.promplate.dev/hmr/mcp.

key features of HMR?

  • Provides comprehensive documentation for the HMR library.
  • Allows for hot module replacement in Python applications.
  • Easy access to source code and examples.

use cases of HMR?

  1. Streamlining the development process by enabling live updates.
  2. Reducing downtime during development by avoiding full page reloads.
  3. Enhancing developer experience with real-time feedback.

FAQ from HMR?

  • What is Hot Module Replacement?

Hot Module Replacement is a feature that allows modules to be updated at runtime without a full reload.

  • Where can I find the documentation?

The documentation is available at HMR Docs.

  • Is HMR compatible with all Python projects?

HMR is designed to work with various Python projects, especially those that require dynamic updates.

Server Config

{
  "mcpServers": {
    "hmr-docs": {
      "type": "http",
      "url": "https://pyth-on-line.promplate.dev/hmr/mcp"
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
Muspi Merol
Star
-
Language
-
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