MCP.so
ログイン
M

MCP Dingtalk Doc

@hykfft

基本情報

カテゴリ

その他

トランスポート

stdio

作者

hykfft

投稿者

振宇 于

MCP Dingtalk Doc について

概要はまだありません

#mcp-dingtalk-doc#document-parser#html-generator

MCP Dingtalk Doc の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "dingtalk-doc": {
      "command": "python3",
      "args": [
        "~/Documents/AIGC/dingtalk_api/mcp_dingtalk_doc/server.py"
      ],
      "env": {
        "DINGTALK_COOKIE": "你的Cookie",
        "DINGTALK_DOC_OUTPUT_DIR": "~/Documents/cursor-mcp/dingDoc"
      }
    }
  }
}

MCP Dingtalk Doc のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Mcp Dingtalk Doc?

Mcp Dingtalk Doc is an MCP server that parses DingTalk document content and generates styled HTML output. It is intended for users who need to extract and view DingTalk documents programmatically. The server was tested on macOS only.

How to use Mcp Dingtalk Doc?

Install from source with pip install -e . or via uv, set the DINGTALK_COOKIE environment variable, then run server.py. Configure the server in any MCP‑compatible client (e.g., Cursor). Two tools are exposed: parse_document (saves files) and get_html (returns HTML without saving). Provide a DingTalk document URL or node ID as input.

Key features of Mcp Dingtalk Doc

  • Full GET → extract dentryKey → POST → HTML pipeline
  • Supports paragraphs, tables, images, and code blocks
  • Beautiful rendering with gradient UI and dark code theme
  • One‑click copy for code blocks
  • Accepts full URL or NODE_ID as input
  • Auto‑archives output in per‑node folders

Use cases of Mcp Dingtalk Doc

  • Analyze a DingTalk document and generate a local HTML copy
  • Embed DingTalk document content into other tools via MCP
  • Perform quick document inspection without manual navigation
  • Archive documents with structured JSON data and rendered HTML

よくある質問

1

What are the runtime requirements?

Python 3.10 or higher is required. The server was tested on macOS.

2

How do I obtain the DingTalk cookie?

Open a DingTalk document in a browser, press F12, go to the Network tab, refresh the page, and copy the `Cookie` field from any request.

3

What files does `parse_document` produce?

It creates a folder containing four files: `{NODE_ID}_mainsite.json`, `{NODE_ID}_document.json`, `{NODE_ID}_content.json`, and `{NODE_ID}.html`.

4

What are known limitations?

OSS‑encrypted document content is not fully decrypted. Some elements (lists, blockquotes, etc.) are not yet supported. The cookie must be renewed when the session expires.

5

Which transport does the server use?

It uses the standard MCP protocol with stdio transport, invoked via `python3 server.py`.

コメント

「その他」の他のコンテンツ