@cosogi/rhwp-mcp
v0.1.4
Published
Unofficial MCP server for rhwp document text and memo tools
Maintainers
Readme
@cosogi/rhwp-mcp
Unofficial fork package for rhwp-based document tooling. This package is not published by, endorsed by, or affiliated with the upstream rhwp maintainers.
This MCP server is built from the c0sogi/rhwp fork and currently exposes
text and memo-oriented tools over the @cosogi/rhwp-core WASM package.
Usage
Run the server with npm:
npx -y @cosogi/rhwp-mcpThe command uses stdio MCP transport. When started directly it waits silently for an MCP client; no startup banner is printed to stdout.
Example MCP client configuration:
{
"mcpServers": {
"rhwp": {
"command": "npx",
"args": ["-y", "@cosogi/rhwp-mcp"]
}
}
}Tools
rhwp_version: returns the MCP package version and underlying rhwp WASM version.rhwp_document_info: loads a.hwpor.hwpxfile and returns document metadata.rhwp_page_text_context: returns LLM-oriented page text context.rhwp_search_text: searches page text, optionally across all pages.rhwp_page_memos: returns memos on a page.rhwp_list_memos: lists memos across all pages, including HWPMEMO_LISTrecords joined to%unkMEMO/...anchors and HWPXfieldBegintype="MEMO"entries when available.rhwp_search_memos: searches memos, optionally across all pages.
All document tools accept an absolute or process-relative inputPath.
Anchored memo entries include memo_index, date/created_at, author,
text/content, and a location object with structural position fields such
as page, section, paragraph, record_index or xml_file,
anchor_text, nearby text, and table-container hints. Entries that cannot be
mapped to a page are also returned in unpaged_memos with page: null.
Current Scope
This first npm MCP package intentionally stays small: it uses the published WASM package and provides text/memo APIs that work in Node without native binary helpers. Page image export and native rendering helpers are not included yet.
