This should resolve the TypeError: 'NoneType' object is not callable that was occurring because the handler was implicitly returning None.
With this modification to the mcpm library source code (which OpenHands uses), the /messages endpoint should now function correctly without crashing.

This commit introduces documentation for the `mcpm share` command in the following places:

- README.md: Added a new section explaining the command, its options, and usage examples.
- README.zh-CN.md: Added a corresponding translated section.
- pages/index.html: Added a new section to the website describing the command and its usage, consistent with other documented commands.

The `mcpm share` command allows you to expose a local MCP server (given by a shell command) to a public URL by using `mcp-proxy` and creating a tunnel.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

…lity (#166)

The `fcntl` module is not available on Windows, and its direct import
was causing `ImportError` when `mcpm share` was invoked or its module
(src/mcpm/commands/share.py) was loaded on Windows systems.

This commit makes the import and usage of `fcntl` within the
`make_non_blocking` function conditional on `os.name == 'posix'`.
On non-POSIX systems (like Windows), the function will now do nothing.

The existing code for reading from subprocess pipes in `mcpm share`
utilizes `select.select()` with timeouts and handles `IOError`/`OSError`
exceptions. This setup is expected to provide sufficient non-blocking
behavior for reading subprocess output on Windows, even without an
explicit `fcntl` call to set `O_NONBLOCK`.

Note: Full dynamic testing of `mcpm share` on a Windows-like environment
was not possible due to a Python version mismatch (environment: 3.10.17,
project requires: >=3.11) in the available testing sandbox. This change
addresses the direct `ImportError`.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

## [1.13.2](v1.13.1...v1.13.2) (2025-06-05)

### Bug Fixes

* trigger semantic release for Windows compatibility fix ([16b5e44](16b5e44))