hwpx-mcp-server — 호환 배포
이 이름은 6.0.0부터 얇은 셸입니다. 실제 코드는
python-hwpx-automation에
있습니다.
응용 계층 5만 줄 중 MCP 전송은 4%뿐이라, 그 4%의 이름이 전체를 대표하고 있었습니다. 이름을 제자리로 옮기되 기존 설치와 MCP 설정은 그대로 둡니다.
pip install hwpx-mcp-server # 계속 동작 — automation[mcp]를 끌어옵니다
pip install python-hwpx-automation # 새 이름. MCP 없이 파이썬 API만
기존 hwpx-mcp-server 명령은 6.x 호환 alias로 유지됩니다. 정식 MCP 명령은
hwpx-automation-mcp, MCP serverInfo.name은 python-hwpx-automation입니다.
호스트 설정의 hwpx key는 protocol identity가 아니라 각 호스트의 local alias입니다.
import hwpx_mcp_server와 공개 deep import는 6.x 동안 동작하며
DeprecationWarning을 냅니다. 새 이름은 hwpx_automation입니다. 제거는 7.0
이전에는 하지 않으며 최소 90일 공개 관찰과 별도 오너 승인이 필요합니다.
셸의 리다이렉트는 런타임 전용이라 mypy/pyright 같은 정적 타입 검사기는 옛
경로를 해석하지 못합니다. 타입 검사가 필요한 코드는 hwpx_automation을 직접
import하세요 — 그쪽이 py.typed를 배포합니다.
importlib.resources의 package data는 복제하지 않습니다. 리소스 소비자는
importlib.resources.files("hwpx_automation")을 사용해야 하며, 호환 셸에는
shim 외의 구현·데이터 사본이 없습니다.
Metadata
Release files for hwpx-mcp-server 7.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| hwpx_mcp_server-7.4.1.tar.gz | 9.4 kB | With provenance | Details for hwpx_mcp_server-7.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hwpx_mcp_server-7.4.1-py3-none-any.whl | Python 3 | none | any | Details for hwpx_mcp_server-7.4.1-py3-none-any.whl |
Total release size: 19.2 kB
Release files / hwpx_mcp_server-7.4.1.tar.gz
| Download URL | hwpx_mcp_server-7.4.1.tar.gz |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
409ccd6727d158dc78bee5b44c17d1c557cbece569c1d401e7d2190c44431c27
|
|
BLAKE2b-256 checksum How to use checksums |
da99ee13f2bcc901c52b8571b71127ab0da2067f90532499e4ec606380237a23
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logRelease files / hwpx_mcp_server-7.4.1-py3-none-any.whl
| Download URL | hwpx_mcp_server-7.4.1-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
473987aebdc81a5f0354891c5d3e767cfaf4e46c79ff0b5658e3b3da2387e0f2
|
|
BLAKE2b-256 checksum How to use checksums |
f75e9799069f05d727f8b62b2d88af1dd2c90fbc36908959405db4aaa3573024
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logSecurity for hwpx-mcp-server 7.4.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for hwpx_mcp_server-7.4.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.