{
  "type": "http",
  "url": "https://py3.online/hmr/mcp"
}
Or use with mcp-remote:
{
  "type": "stdio",
  "command": "npx",
  "args": [
    "mcp-remote",
    "https://py3.online/hmr/mcp"
  ]
}

HMR Docs MCP Server

Access our documentation through the Model Context Protocol.

A Model Context Protocol (MCP) server implementation that provides documentation for reactive programming and hot reloading in python.

Features

  • Fetch guides and examples of reactive programming and hot reloading

  • Read detailed conceptual explanations and architecture overview

  • Retrieve complete HMR library source code

  • Get docs for integration libraries (like uvicorn) (coming soon)

  • Ask our built-in AI assistant for help with HMR concepts and usage (coming soon)


Installation

We only support the Streamable HTTP protocol, which is the latest and recommended way. The MCP server endpoint is:

https://py3.online/hmr/mcp

In most MCP clients, your configuration will look like this:

{
  "mcpServers": {
    "hmr-docs": {
      "type": "http",
      "url": "https://py3.online/hmr/mcp"
    }
  }
}

You can also use the mcp-remote CLI to proxy the connection:

npx mcp-remote https://py3.online/hmr/mcp

The config file would like this:

{
  "mcpServers": {
    "hmr-docs": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://py3.online/hmr/mcp"
      ]
    }
  }
}

Application specific shortcuts

For convenience, here are some shortcuts for popular MCP clients.

Cursor

Directly use the remote server Install MCP Server or use the stdio proxy Install MCP Server.

Claude Code

claude mcp add --transport http hmr-docs https://py3.online/hmr/mcp

or

claude mcp add --transport stdio hmr-docs npx mcp-remote https://py3.online/hmr/mcp

VS Code (GitHub Copilot)

Direct links: Install the remote server or Install the stdio proxy.


Available tools

Under construction...


Troubleshooting

  • Test the endpoint directly: curl https://py3.online/hmr/mcp

  • Verify the config matches the expected schema (each client may have slightly different config flavors)