hmr
Server Details
Docs for hot-module-reload and reactive programming for Python (hmr on PyPI)
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- promplate/hmr
- GitHub Stars
- 47
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.1/5 across 3 of 3 tools scored. Lowest: 3.5/5.
The three tools have clearly distinct purposes: learn-hmr-basics provides conceptual explanations, view-hmr-core-sources shows the library's source code, and view-hmr-unit-tests offers practical examples via tests. There is no overlap in functionality, and the descriptions explicitly guide when to use each tool, preventing confusion.
All tool names follow a consistent verb-object pattern using snake_case: learn-hmr-basics, view-hmr-core-sources, and view-hmr-unit-tests. The naming is predictable and readable, with 'learn' for conceptual tools and 'view' for code/tests, maintaining a clear convention throughout.
With 3 tools, this server is well-scoped for its purpose of exploring the HMR library. Each tool serves a distinct role in the learning workflow (basics, source code, tests), and the count is appropriate for a focused educational or documentation server without being too sparse or overwhelming.
The tool set covers the core aspects of learning and using the HMR library: conceptual understanding, source code inspection, and practical examples. However, there is a minor gap in direct execution or interactive tools (e.g., running code or applying HMR in real-time), which might limit hands-on usage but is not critical for the educational focus.
Available Tools
3 toolslearn-hmr-basicslearn-hmr-basicsRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
view-hmr-core-sourcesview-hmr-core-sourcesRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
view-hmr-unit-testsview-hmr-unit-testsRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!