Skip to main content
mcpSource-backed

Kordoc MCP Server

MCP server for parsing Korean HWP, HWPX, HWPML, PDF, XLSX, and DOCX files into Markdown, with tools for metadata extraction, page ranges, tables, document diffs, form extraction, and HWPX form filling.

by chrisryugj · submitted by oktofeesh1·added 2026-06-06·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://raw.githubusercontent.com/chrisryugj/kordoc/main/README-EN.md, https://github.com/chrisryugj/kordoc
Brand
kordoc
Brand domain
github.com
Safety notes
Kordoc MCP Server reads local document files by absolute path and, by default, does not restrict access to a workspace directory., The MCP source allowlists `.hwp`, `.hwpx`, `.pdf`, `.xlsx`, and `.docx` files, resolves symlinks, and applies a 500MB full-parse file limit., Metadata-only parsing has a smaller 50MB limit, while archive, PDF, HWP5, and table parsers have additional resource limits documented in the security policy., Form filling can write Markdown or HWPX files to an `output_path`; require confirmation before allowing an agent to create or overwrite documents., Kordoc processes untrusted binary formats; keep the Node.js runtime and parser dependencies updated and avoid running it on high-privilege accounts., The CLI also has watch and webhook flows; keep those separate from the MCP server unless you have reviewed outbound notification behavior.
Privacy notes
Parsed content can include full document text, tables, titles, authors, page counts, metadata, warnings, form labels, and filled values., Document paths and resolved output paths can appear in MCP responses, CLI output, logs, or saved artifacts., Government, legal, HR, finance, or customer documents may contain sensitive identifiers that become Markdown or JSON in the MCP client context., HWPX form filling can preserve and rewrite original templates; store generated files only in approved directories., Webhook or watch-mode workflows can send converted document information to third-party endpoints if enabled outside the MCP server.
Author
chrisryugj
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

10 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Includes a review or approval gate.

0/5 ready
Install & runtime2Network & hosting1Review & approval1General110 minutes

Safety & privacy surface

Safety & privacy surface

6 safety and 5 privacy notes across 4 risk areas. Review closely: network access.

4 areas
  • SafetyLocal filesKordoc MCP Server reads local document files by absolute path and, by default, does not restrict access to a workspace directory.
  • SafetyLocal filesThe MCP source allowlists `.hwp`, `.hwpx`, `.pdf`, `.xlsx`, and `.docx` files, resolves symlinks, and applies a 500MB full-parse file limit.
  • SafetyGeneralMetadata-only parsing has a smaller 50MB limit, while archive, PDF, HWP5, and table parsers have additional resource limits documented in the security policy.
  • SafetyLocal filesForm filling can write Markdown or HWPX files to an `output_path`; require confirmation before allowing an agent to create or overwrite documents.
  • SafetyExecution & processesKordoc processes untrusted binary formats; keep the Node.js runtime and parser dependencies updated and avoid running it on high-privilege accounts.
  • SafetyNetwork accessThe CLI also has watch and webhook flows; keep those separate from the MCP server unless you have reviewed outbound notification behavior.
  • PrivacyGeneralParsed content can include full document text, tables, titles, authors, page counts, metadata, warnings, form labels, and filled values.
  • PrivacyLocal filesDocument paths and resolved output paths can appear in MCP responses, CLI output, logs, or saved artifacts.
  • PrivacyGeneralGovernment, legal, HR, finance, or customer documents may contain sensitive identifiers that become Markdown or JSON in the MCP client context.
  • PrivacyLocal filesHWPX form filling can preserve and rewrite original templates; store generated files only in approved directories.
  • PrivacyNetwork accessWebhook or watch-mode workflows can send converted document information to third-party endpoints if enabled outside the MCP server.

Disclosure: Community-maintained MIT MCP server and document parser for Korean HWP, HWPX, HWPML, PDF, XLSX, and DOCX workflows.

Safety notes

  • Kordoc MCP Server reads local document files by absolute path and, by default, does not restrict access to a workspace directory.
  • The MCP source allowlists `.hwp`, `.hwpx`, `.pdf`, `.xlsx`, and `.docx` files, resolves symlinks, and applies a 500MB full-parse file limit.
  • Metadata-only parsing has a smaller 50MB limit, while archive, PDF, HWP5, and table parsers have additional resource limits documented in the security policy.
  • Form filling can write Markdown or HWPX files to an `output_path`; require confirmation before allowing an agent to create or overwrite documents.
  • Kordoc processes untrusted binary formats; keep the Node.js runtime and parser dependencies updated and avoid running it on high-privilege accounts.
  • The CLI also has watch and webhook flows; keep those separate from the MCP server unless you have reviewed outbound notification behavior.

Privacy notes

  • Parsed content can include full document text, tables, titles, authors, page counts, metadata, warnings, form labels, and filled values.
  • Document paths and resolved output paths can appear in MCP responses, CLI output, logs, or saved artifacts.
  • Government, legal, HR, finance, or customer documents may contain sensitive identifiers that become Markdown or JSON in the MCP client context.
  • HWPX form filling can preserve and rewrite original templates; store generated files only in approved directories.
  • Webhook or watch-mode workflows can send converted document information to third-party endpoints if enabled outside the MCP server.

Prerequisites

  • Node.js 18 or newer.
  • A local MCP client that can launch stdio servers with access to the documents you want parsed.
  • Optional `pdfjs-dist` support if you need PDF parsing in environments where the package is not already installed.
  • Approved directories for source documents and generated Markdown or HWPX output.
  • Hancom Office on Windows if you rely on the repository's documented COM fallback for protected HWP or HWPX files.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Tool listing metadata
Disclosure
Community-maintained MIT MCP server and document parser for Korean HWP, HWPX, HWPML, PDF, XLSX, and DOCX workflows.
Full copyable content
{
  "mcpServers": {
    "kordoc": {
      "command": "npx",
      "args": ["-y", "kordoc", "mcp"]
    }
  }
}

About this resource

Content

Kordoc MCP Server connects Claude and other MCP clients to the Kordoc document parser. It focuses on Korean document workflows where HWP, HWPX, HWPML, PDF, XLSX, and DOCX files need to become Markdown or structured metadata before an AI assistant can review them.

Use it when Claude needs supervised local access to parse documents, inspect metadata, extract a page range, pull one table, compare two versions, detect form fields, or fill an HWPX form template.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, English README, npm metadata, license, security policy, MCP server source, CLI source, and parser exports for current setup and behavior details.

Features

  • Parse HWP, HWPX, HWPML, PDF, XLSX, and DOCX files into Markdown.
  • Detect document format from file headers.
  • Extract document metadata without a full parse when supported.
  • Parse selected page or section ranges.
  • Extract a specific table by index.
  • Compare two documents across supported formats.
  • Extract structured form fields from Korean form templates.
  • Fill form fields and optionally write Markdown or HWPX output.
  • Return outlines, warnings, and quality signals when parser support is available.

Installation

Run the setup command from the upstream package:

npx -y kordoc setup

Then add the MCP server to your client configuration:

{
  "mcpServers": {
    "kordoc": {
      "command": "npx",
      "args": ["-y", "kordoc", "mcp"]
    }
  }
}

The npm package exposes both a kordoc CLI and a kordoc-mcp binary. The README recommends launching the MCP server through the kordoc mcp subcommand.

Use Cases

  • Convert Korean public-sector HWP or HWPX files into Markdown for Claude review.
  • Ask Claude to extract metadata, document outlines, warnings, or table content before summarizing a file.
  • Compare old and new versions of a document and identify added, removed, or changed blocks.
  • Pull fields from an application template and draft candidate fill values for user approval.
  • Fill an HWPX template and write the result to an approved output path.
  • Flag PDFs that likely need OCR before sending them through a separate OCR workflow.

Safety and Privacy

Kordoc MCP Server is a local document parser, not a sandbox. It resolves absolute paths and can read any allowlisted document file the server process can access, so run it under a least-privilege account and keep sensitive directories out of reach.

Treat parsed Markdown, metadata, form values, document paths, warnings, and generated HWPX files as sensitive. Review output paths before allowing writes, and avoid enabling watch or webhook workflows unless their network behavior is part of your data-handling plan.

Source citations

Add this badge to your README

Show that Kordoc MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/kordoc-mcp-server.svg)](https://heyclau.de/entry/mcp/kordoc-mcp-server)

How it compares

Kordoc MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

MCP server for parsing Korean HWP, HWPX, HWPML, PDF, XLSX, and DOCX files into Markdown, with tools for metadata extraction, page ranges, tables, document diffs, form extraction, and HWPX form filling.

Open dossier

Official Agentset MCP server that lets Claude retrieve cited knowledge-base results from an Agentset namespace through the `knowledge-base-retrieve` tool, with optional tenant scoping and custom tool descriptions.

Open dossier

Unity MCP server, plugin, CLI, and skill generator for controlling Unity Editor and runtime projects from MCP clients through built-in game-dev tools.

Open dossier

MCP server for Anki flashcards that lets Claude review cards, manage decks, create and update notes, handle tags and media, inspect stats, and drive Anki desktop GUI workflows.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandAgentset logoAgentsetAI Game Developer logoAI Game DeveloperAnki MCP Server logoAnki MCP Server
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorchrisryugjAgentsetIvan MurzakAnkiMCP
Added2026-06-062026-06-062026-06-062026-06-06
Platforms
Harness
Source repo
Safety notesKordoc MCP Server reads local document files by absolute path and, by default, does not restrict access to a workspace directory. The MCP source allowlists `.hwp`, `.hwpx`, `.pdf`, `.xlsx`, and `.docx` files, resolves symlinks, and applies a 500MB full-parse file limit. Metadata-only parsing has a smaller 50MB limit, while archive, PDF, HWP5, and table parsers have additional resource limits documented in the security policy. Form filling can write Markdown or HWPX files to an `output_path`; require confirmation before allowing an agent to create or overwrite documents. Kordoc processes untrusted binary formats; keep the Node.js runtime and parser dependencies updated and avoid running it on high-privilege accounts. The CLI also has watch and webhook flows; keep those separate from the MCP server unless you have reviewed outbound notification behavior.The MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace. The `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance. Namespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent. API keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager. Custom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows.AI Game Developer can create, move, copy, modify, and delete Unity assets, scenes, GameObjects, components, scripts, packages, and generated project files. Tools include dynamic C# script execution, C# reflection method lookup and calls, package installation/removal, Unity test execution, editor state changes, play mode control, screenshots, and profiler access. The MCP server supports streamable HTTP and stdio; HTTP deployments should require a bearer token and stay bound to trusted interfaces. Server variables include optional authorization and webhook settings; webhook endpoints can receive tool, prompt, resource, connection, and authorization events. Unity runtime connections can expose compiled game state or in-game behavior to an MCP client, not just editor-only project data. Use source control, backups, tool filtering, and explicit review before allowing destructive tools such as asset deletion, package removal, script execution, or reflection calls.Anki MCP Server can create, update, delete, move, tag, rate, and sync cards and notes through AnkiConnect. Destructive tools include note deletion, media deletion, unused-tag clearing, deck moves, tag replacement, model styling changes, and review rating actions that affect scheduling. The server supports read-only mode that blocks exposed write actions, but users should still review tool calls before enabling unrestricted study or collection-management workflows. Media tools can store files from local paths, URLs, or base64 data and can retrieve media as base64 content. GUI tools can open Anki windows, select cards, edit notes, show answers, and undo the last Anki action. Remote tunnel or ngrok-style setups expose local Anki to cloud-hosted AI clients and require careful authentication, origin, and URL-sharing controls.
Privacy notesParsed content can include full document text, tables, titles, authors, page counts, metadata, warnings, form labels, and filled values. Document paths and resolved output paths can appear in MCP responses, CLI output, logs, or saved artifacts. Government, legal, HR, finance, or customer documents may contain sensitive identifiers that become Markdown or JSON in the MCP client context. HWPX form filling can preserve and rewrite original templates; store generated files only in approved directories. Webhook or watch-mode workflows can send converted document information to third-party endpoints if enabled outside the MCP server.Retrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data. Retrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry. Tenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base. Do not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files.Tool calls may expose Unity project paths, asset names, scene hierarchy, serialized object data, scripts, logs, screenshots, profiler metrics, test output, package metadata, and runtime state. MCP config files and Unity plugin config can contain server URLs, connection modes, bearer tokens, authorization settings, enabled tool IDs, and cloud or local endpoint details. Optional webhooks can receive tool, prompt, resource, connection, authorization, and token-bearing request data. Screenshots from Game View, Scene View, cameras, or isolated GameObjects may include proprietary artwork, level design, UI, debug overlays, or unreleased game content. Generated skills and AI-client configuration files can reveal available tools, project structure, installed packages, and local workflow assumptions.Tool calls can expose deck names, note fields, card contents, tags, review history, media filenames, base64 media, selected notes, collection stats, scheduling metadata, and AnkiConnect errors. Flashcards may contain medical, language-learning, school, work, personal, customer, or confidential study material. Sync can send Anki collection changes to AnkiWeb according to the user's Anki account and sync settings. Local media file paths, URLs imported into cards, and GUI-selected note IDs can enter MCP client context and model logs. Remote tunnel providers and hosted clients may process connection metadata or traffic according to their own policies.
Prerequisites
  • Node.js 18 or newer.
  • A local MCP client that can launch stdio servers with access to the documents you want parsed.
  • Optional `pdfjs-dist` support if you need PDF parsing in environments where the package is not already installed.
  • Approved directories for source documents and generated Markdown or HWPX output.
  • Agentset account or self-hosted Agentset deployment with a populated namespace.
  • Agentset API key with access to the namespace Claude should query.
  • Node.js 18.17 or newer for running the `@agentset/mcp` package.
  • Namespace ID selected with `--ns` or `AGENTSET_NAMESPACE_ID`.
  • Unity project using Unity 2022.3 or newer for the current package metadata.
  • Unity Hub or a local Unity Editor installation.
  • Node.js 20.19 or newer, or Node.js 22.12 or newer, for `unity-mcp-cli`.
  • An MCP client such as Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, GitHub Copilot, Cline, or another supported client.
  • Anki Desktop installed and running.
  • The AnkiConnect add-on installed in Anki.
  • Node.js 22.12 or newer for the npm package path.
  • Review of which decks, cards, tags, media files, and note types the MCP client may access.
Install
npx -y kordoc setup
Run `npx @agentset/mcp --ns <namespace-id>` with `AGENTSET_API_KEY` set in the MCP server environment.
npm install -g unity-mcp-cli && unity-mcp-cli install-plugin ./MyUnityProject
npx -y @ankimcp/anki-mcp-server --stdio
Config
{
  "mcpServers": {
    "kordoc": {
      "command": "npx",
      "args": [
        "-y",
        "kordoc",
        "mcp"
      ],
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "agentset": {
      "command": "npx",
      "args": ["-y", "@agentset/mcp@latest", "--ns", "ns_xxx"],
      "env": {
        "AGENTSET_API_KEY": "agentset_xxx"
      }
    }
  }
}
Manual-only setup:
npm install -g unity-mcp-cli
unity-mcp-cli install-plugin ./MyUnityProject
unity-mcp-cli open ./MyUnityProject
{
  "mcpServers": {
    "anki": {
      "command": "npx",
      "args": [
        "-y",
        "@ankimcp/anki-mcp-server",
        "--stdio"
      ],
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.