Docs for hot-module-reload and reactive programming for Python (`hmr` on PyPI)
dev.promplate/hmr MCP Server
The Model Context Protocol (MCP) server “dev.promplate/hmr” provides access to documentation for hot-module-reload and reactive programming for Python, where “hmr” is also published on PyPI. The server is associated with 3 tools and is focused on HMR concepts and related hot-reload functionality.
🛠️ Key Features
3 tools
Hot-reload support via an on-demand “hot-reload tool”
Reactive programming engine/framework for Python
🚀 Use Cases
Hot Module Reload (HMR) in Python applications
Building progressive-yet-intuitive reactive workflows
Using fine-grained, on-demand hot reload during development
⚡ Developer Benefits
Pythonic, flexible approach to reactive programming
Tooling for hot reloading at a fine-grained level
References and pointers to HMR documentation (PyPI and linked HMR page)
⚠️ Limitations
Available information is limited to the provided description, tool count (3), and topics; no additional capabilities are specified.
A brief and concise explanation of the `hmr` library.
This tool provides information on how to use reactive programming or use hot module reloading in Python. As long as the user mentions HMR / Reactive Programming, this tool must be called first! Don't manually view the resource, call this tool instead.
Parameters
No parameters.
Raw schema
{
"type": "object",
"properties": {}
}
view-hmr-core-sources
The full source code (core only) of the HMR library.
Always call `learn-hmr-concepts` to learn the core concepts before calling this tool. These files are the full source code of the HMR library, which would be very helpful because good code are self-documented. For a brief and concise explanation, please refer to the `hmr-docs://about` MCP resource. Make sure you've read it before calling this tool. To learn how to use HMR for reactive programming, read the unit tests later. The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.
Parameters
No parameters.
Raw schema
{
"type": "object",
"properties": {}
}
view-hmr-unit-tests
The unit tests (code examples) for HMR.
Always call `learn-hmr-basics` and `view-hmr-core-sources` to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.
HMR provides a pythonic, flexible, progressive-yet-intuitive reactive programming engine / framework, and on top of that, a fine-grained, on-demand hot-reload tool.
In Python, HMR stands for Hot Module Reload, though in JavaScript it commonly refers to Hot Module Replacement—essentially the same concept. It is a feature that allows part of your app to be updated at runtime without a full rerun, without needing to restart the entire process.
Unlike traditional Python reloaders (such as watchfiles CLI, uvicorn --reload, or Flask's debug mode), HMR is much more efficient and robust. These tools typically restart the entire process whenever a file changes, which is wasteful. HMR instead intelligently reruns only what's necessary, keeping your app state intact.
Imagine you're developing an ML service using FastAPI with a model that requires 5 seconds to initialize. When using uvicorn --reload, any change—even updating a simple docstring—triggers a full process restart, forcing you to wait those 5 seconds every time. It's as frustrating as encountering a red light at every intersection.
HMR offers a smoother experience. Changes take effect instantly because HMR is variable-level fine-grained: your codebase functions like a dependency graph—when you modify a file, HMR only reruns the affected modules from that modified module up to your entry point file. If you update a variable that nothing depends on, nothing happens.
CAUTION
What this package is not?
hmr should not be confused with client-side hot reloading that updates browser content when server code changes. This package implements server-side HMR, which only reloads python code upon changes.
Usage
The quickest way to experience HMR is through the CLI:
sh
pip install hmr
hmr path/to/your/entry-file.py
Parameters work exactly like python command, except your files now hot-reload on changes. Try saving files to see instant updates without losing state.
If you have uv installed, you can try hmr directly with:
sh
uvx hmr path/to/your/entry-file.py
Ecosystem
HMR provides a rich ecosystem of tools for different Python development scenarios:
Browser auto-refresh middleware for automatic page reloading
TIP
The hmr ecosystem is essentially stable and production-ready for most use cases. It has been carefully designed to handle many common edge cases and Pythonic magic patterns, including lazy imports, dynamic imports, module-level __getattr__, decorators, and more. However, circular dependencies in some edge cases may still cause unexpected behavior. Use with caution if you have a lot of code in __init__.py.
mcp/ - MCP server with live code updates without connection drops
Motivation
HMR is already a common feature in the frontend world. Web frameworks like Vite supports syncing changes to the browser without a full refresh. Test frameworks like Vitest supports on-demand updating test results without a full rerun.
So, why not bring this magic to Python?
How it works
HMR uses runtime dependency tracking instead of static analysis to achieve fine-grained reactivity:
Signal & Observer Pattern: Signal is an alternative to the observer pattern. I implemented a simple signal system to notify changes whenever data is accessed or modified.
Custom Module Class: I implemented a custom Module class which tracks every __getattr__ and __setattr__ call. When a variable is changed, it notifies the modules that use it. This notification is recursive but fine-grained.
File System Tracking: watchfiles is used to detect file changes. If a change's path is a Python module that has been imported, it triggers reloading of affected code. Additionally, HMR monitors all file reads (via sys.addaudithook) so changes to non-Python files (YAML, JSON, etc.) also trigger appropriate reloads.
This runtime approach enables variable-level granularity and can track dependencies across any file type—far more precise than static analysis.
Contributing
This might just be one of the first variable-level fine-grained HMR frameworks in the Python ecosystem—and honestly, the real magic lies in the ecosystem we build around it.
Pair uvicorn + hmr, and you've got yourself a Vite-like development experience. Combine pytest + hmr for test-driven development that rivals Vitest. The possibilities with other libraries? Endless. Let's brainstorm together—who knows what fun (or mildly chaotic) things we might create!
TIP
A little backstory: the code for hmr lives in another repo because, truth be told, I wasn't planning on building an HMR framework. This started as an experiment in bringing reactive programming to Python. Along the way, I realized: why not make a module's globals reactive? And that's how HMR was born! While it began as a side project, I see tremendous potential in it for advancing Python's development experience.
For now, this repo is home to the main implementation and examples. If you think HMR has potential, or you just want to throw ideas around, I'd love to hear from you. We believe that the Python community deserves a more dynamic, responsive development experience, and we're excited to see where this can take us!