制限されたアクセス権限のもとで、ローカルのドキュメント、メールストア、および請求書の検査、検索、取得、変換を行います。
別名 EvotecIT/OfficeIMO, officeimo
- スター
- 704
- ツール
- —
- ダウンロード数(30日間)
- —
- 最新バージョン
- 3.5.1
- 最終コミット
- 2026年11月15日
- ライセンス
- MIT
OfficeIMO Document Tools MCPとは
制限されたアクセス権限のもとで、ローカルのドキュメント、メールストア、および請求書の検査、検索、取得、変換を行います。
プロジェクトのREADMEから生成された概要
OfficeIMO Document Tools MCP server について
OfficeIMO Document Toolsは、検査、変換、抽出を通じてドキュメントのライフサイクルを管理するためのコマンドラインインターフェースを提供します。PDF、請求書、およびDOCX、XLSX、PPTXを含むさまざまなオフィス形式などのローカルファイルを処理する必要がある開発者や自動化ワークフロー向けに設計されています。このツールはMCPクライアント用のローカルstdioサーバーとして動作するため、ユーザーは環境変数OFFICEIMO_MCP_ALLOWED_ROOTSを使用して許可するディレクトリを定義する必要があります。
ユーザーは、PDFの分割、最適化、サニタイズ、またはTesseractなどのOCRプロバイダーを使用した検索可能なスキャンの作成といった複雑なPDF操作を実行できます。また、このサーバーは特化した請求書ワークフローも処理し、XML形式の請求書の検査、検証、および異なる標準規格やハイブリッドPDF形式への変換を可能にします。JSON出力からパスワードやドキュメントのテキストなどの機密情報を除外することで、データプライバシーのための保護機能が組み込まれています。システムは、バッチ処理タスク中の安定した実行を確保するために、入出力サイズの制限を管理します。
できること
- 1ドキュメント形式の一括変換開発者はバッチワークフローを実行して、さまざまなオフィスファイルが含まれるディレクトリ全体をPDF形式に変換できます。
- 2XML請求書の検証と編集AIエージェントは、XML形式の請求書を検査してモデルのエラーを確認したり、請求書番号や発行日などの特定のフィールドを更新したりできます。
- 3検索可能なPDFスキャンの作成OCRプロバイダーを介してテキストレイヤーを追加することで、標準的なPDFを検索可能なドキュメントに変換できます。
- 4機密性の高いPDFドキュメントのサニタイズユーザーは、配布しても安全であることを確認するために、レポートのサニタイズ済みバージョンを作成できます。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
設定
OFFICEIMO_MCP_ALLOWED_ROOTS必須Authorized document and output folders. Separate roots with ':' on macOS/Linux or ';' on Windows. Registry launch requires dotnet dnx with --yes support (qualified with .NET SDK 10.0.113).
| 名前 | 説明 | 種類 |
|---|---|---|
| OFFICEIMO_MCP_ALLOWED_ROOTS | Authorized document and output folders. Separate roots with ':' on macOS/Linux or ';' on Windows. Registry launch requires dotnet dnx with --yes support (qualified with .NET SDK 10.0.113). | 必須 |
自動チェック
実行日 2026年11月12日完全なレポート →まだ検証されていません。サーバーには80点のスコア、重大な問題がないこと、および検証に必要な十分なデータが必要です。 チェックの仕組み · 点数を上げるための改善点
- ソースリポジトリがリンクされており、アクセス可能合格
- オープンソースライセンス (OSI)合格
- 過去1年以内にコミットまたはリリースあり合格
- パッケージ名が有名なパッケージに酷似していない未チェック
- リモートエンドポイントがHTTPSを使用未チェック
- 破壊的なツールがラベル付けされている未チェック
- モデルへの隠れた指示がない合格
- パッケージおよびその依存関係に重大な勧告なし未チェック
README
GitHubで見るOfficeIMO.Tool
OfficeIMO.Tool is the installable command-line interface for OfficeIMO document conversion, extraction, inspection, markup, output, intake, and MCP workflows.
Install
Install it globally from NuGet when you want officeimo available from any directory:
dotnet tool install --global OfficeIMO.Tool
officeimo --version
For a repository-pinned local tool, create or reuse a tool manifest:
dotnet new tool-manifest
dotnet tool install OfficeIMO.Tool
dotnet tool run officeimo help
# The .NET SDK also resolves a manifest-local tool through this shorthand:
dotnet officeimo help
Update or remove a global installation with the standard .NET tool commands:
dotnet tool update --global OfficeIMO.Tool
dotnet tool uninstall --global OfficeIMO.Tool
MCP clients
server.json describes the local STDIO server as io.github.EvotecIT/officeimo, backed by the OfficeIMO.Tool NuGet package. Clients supply OFFICEIMO_MCP_ALLOWED_ROOTS. The agent plugin launches dotnet dnx OfficeIMO.Tool@<package-version> mcp serve --stdio --yes with .NET SDK 10.0.100 or later; the trailing flag accepts the pinned package download on SDKs that prompt, and older SDKs pass it through harmlessly to the MCP host.
Registry clients place the download-consent flag before the package argument. This route requires an SDK whose dotnet dnx --help lists --yes, qualified with SDK 10.0.113. Some other .NET 10 feature bands lack that option; use the plugin's explicit launcher above on those SDKs. The registry entry exposes the same bounded operations as the plugin.
PDF copies and searchable scans
Create a separate PDF, split folder, or searchable scan with an explicit destination:
officeimo pdf extract report.pdf --pages last,1-3 --output selected.pdf
officeimo pdf split report.pdf --pages-per-document 10 --output report-parts
officeimo pdf decrypt protected.pdf --password-env PDF_OWNER_PASSWORD --output clear.pdf
officeimo pdf flatten report.pdf --output raster.pdf --acknowledge-raster-output --dpi 150
officeimo pdf optimize report.pdf --output optimized.pdf
officeimo pdf sanitize report.pdf --output sanitized.pdf
officeimo pdf providers --ocr-provider-assembly ./providers/OfficeIMO.Ocr.Tesseract.dll
officeimo pdf ocr scan.pdf --output searchable.pdf --ocr-provider tesseract-cli --ocr-provider-assembly ./providers/OfficeIMO.Ocr.Tesseract.dll --ocr-language eng
Page selections retain order and repeated pages and support expressions such as
last,1-3, odd, and all,!2. The selected pages are resolved against the captured
input. Existing files or folders require --force; a source or folder containing
it cannot be the destination. Decryption requires the owner password in the named
environment variable. Other protected-document operations retain the PDF engine's
permission and signature policy.
Flattening copies rendered appearances. Native text, forms, links, signatures,
and attachments are omitted, so --acknowledge-raster-output is required.
The managed renderer's fidelity limits still apply. Searchable OCR adds a text
layer to the source pages; confidence does not certify recognition accuracy.
The tool includes no OCR executable or model. Supply a trusted optional provider
deployment with its managed dependencies. OfficeIMO.Ocr.Tesseract registers
tesseract-cli and uses a separately installed Tesseract executable. Repeated
--ocr-option key=value entries configure the provider; executable/model paths
are chosen by the invoking host. See the Tesseract provider options.
These commands emit bounded JSON containing status, artifact paths/counts/bytes,
and diagnostic codes. Document text, recognized words, passwords and provider
messages are excluded. Defaults limit selection to 100 pages or split parts,
input to 256 MiB, output to 512 MiB, and raster work to 25 million pixels per page.
Use the --maximum-pages, --maximum-input-bytes, --maximum-output-bytes, and
--maximum-pixels-per-page options within the ranges listed by officeimo pdf --help.
Invoice workflows
Invoice commands return versioned JSON with separate model, mapping and standards
results. Inspecting an invoice can succeed while reporting invalid model data;
validate returns a failure exit code for those errors. Schema and business-rule
statuses remain NotRun unless standards validation is explicitly configured.
officeimo invoice inspect invoice.xml
officeimo invoice validate invoice.xml
# Replace existing source headers while retaining XML extensions.
officeimo invoice edit invoice.xml --output invoice.edited.xml `
--number INV-002 --issue-date 2026-09-30 --buyer-reference BUYER-002
# Convert with an explicit, pinned target contract.
officeimo invoice convert invoice.xml --output invoice.ubl.xml `
--release En16931_1_3_16 --syntax Ubl --profile En16931
# Create a hybrid invoice with Polish labels and an embedded font.
officeimo invoice hybrid invoice.xml --output invoice.pdf `
--release FacturX_1_09_2_Zugferd_2_5_2 --syntax Cii --profile En16931 `
--language pl-PL --font ./fonts/InvoiceFont.ttf `
--columns Item,Quantity,Unit,NetPrice,Vat,NetAmount `
--unit-display Description --payment-display Description `
--modern --compact-details --page-identity
officeimo invoice batch validate first.xml second.xml --max-items 100 --stop-on-failure
# Validate exact source bytes with pinned authority artifacts and the Saxon runner.
officeimo invoice validate invoice.xml --standards-release En16931_1_3_16 `
--rule-bundle ./rules/xrechnung.zip --saxon-jar ./saxon/saxon-he-12.10.jar
render creates a separate presentation PDF; hybrid embeds the captured CII XML.
An explicit target is required for conversion and rendering. Unmapped source data
and unsupported target fields block those operations. --allow-profile-loss permits only
the documented reductions of lower Factur-X profiles and returns warnings for
them. XML standards validation does not certify the PDF's archival conformance.
edit accepts --number, --issue-date, --due-date, --buyer-reference and
--payment-reference; dates use yyyy-MM-dd. It replaces existing unique
plaintext fields and retains other XML content. Signed XML and unsupported date
representations are blocked. It retains the input syntax/profile and accepts no
target options. A successful edit can report model or mapping errors; inspect
those JSON findings and request standards validation when required. Requested
standards stages must pass on exact edited bytes before publication. Use
batch edit to apply the same captured replacements to several inputs.
File outputs are created atomically and never overwrite existing files. Batch
writing uses --output-directory, naming each output <input-stem>.invoice.xml
or <input-stem>.invoice.pdf. All inputs and destinations are checked before
execution; colliding or existing destinations fail before any output is created.
Batch publication is per item. Limits default to 256 inputs, 64 MiB of combined
input and 64 MiB of returned artifacts. --max-input-bytes and
--max-output-bytes change those combined budgets; each XML input remains limited
to 16 MiB. For the pinned authority downloads and runtime requirements, see the
standards validator guide.
File batches and printing
DOC conversion blocks known legacy import loss by default; --allow-legacy-loss explicitly accepts the reported reductions. TXT conversion treats HTML and Markdown as literal text, detects Unicode BOMs and otherwise uses strict UTF-8. Use --text-encoding and --tab-size for explicit text settings. The adapter's diagnostics remain on standard error.
Batch conversion uses the existing executable workflow catalog. PDF routes include DOC, DOCX, TXT, XLSX, PPTX, HTML, Markdown, RTF, Draw, DjVu and Publisher. Files without an eligible route are counted as skipped. Checkpoints are optional. Resolve relative paths from the directory where the command runs:
officeimo workflow batch --input-directory ./Documents --output ./PDF
# Enable durable checkpoints; rerun to verify and reuse completed artifacts.
officeimo workflow batch --input-directory ./Documents --output ./PDF --checkpoint ./PDF-State
officeimo workflow batch --input-directory ./Documents --output ./PDF --checkpoint ./PDF-State --retry-failed
# Explicit files and other existing conversion targets use the same command.
officeimo workflow batch report.pdf appendix.pdf --output ./HTML --target html
officeimo workflow printers
officeimo workflow printers --paper-sources "Office printer"
officeimo workflow print report.pdf --printer "Office printer" --pages 1-3 `
--pages-per-sheet 2 --copies 1 --duplex long
officeimo workflow print-plan report.pdf --pages-per-sheet 6 --page-subset odd `
--scale custom --custom-scale 40 --alignment bottom-right --margin 18 `
--margin-left 24 --margin-right 24 --color grayscale
Ordinary batches accept --conflict fail|rename|replace. Checkpoint jobs require fail and separate source, output and state trees. Changed completed inputs/settings/resources, altered or missing outputs and existing outputs without a verified receipt require inspection. Concurrency and execution budgets can change without discarding verified artifacts. Item failures produce a nonzero exit code. See the batch contract for resource limits, diagnostics and recorded-artifact reuse across compatible engine updates.
Printer submission uses prepared raster sheets. The returned job identifier proves queue acceptance; physical delivery is unconfirmed. After an interrupted submission, check the queue before retrying. Windows file printers require --output-file naming a new local file. macOS/Linux delivery uses the existing CUPS service boundary and requires its command-line tools.
Both print-plan and print accept 1/2/4/6/9 pages per sheet, --page-subset all|odd|even, nine-position --alignment, and per-edge point margins (--margin-left, --margin-top, --margin-right, --margin-bottom). Odd/even refers to original document page numbers within --pages. --scale custom --custom-scale <percent> uses 1–1000 percent of source physical size and clips overflow. --color grayscale changes the prepared pixels; --color color retains source colors, subject to the device's capabilities. Layout margins do not remove printer hardware margins.
Saved conversion jobs
Save reviewed batch settings without executing them, inspect the plan, then run the same local job from any working directory:
officeimo workflow batch --input-directory ./documents --output ./pdf --checkpoint ./conversion-state --save-job ./monthly.officeimojob.json
officeimo workflow job plan ./monthly.officeimojob.json
officeimo workflow job run ./monthly.officeimojob.json --format ndjson
officeimo workflow job run ./monthly.officeimojob.json --retry-failed
Paths inside the job resolve against its file location. Saving captures portable settings and never reads secret values or converts files. Unknown schema versions, unknown fields and unsupported renderer settings are rejected. A plan reports selection, destinations and collisions without writing outputs or checkpoints; execution revalidates current inputs. Registered iWork routes use the host's ordinary batch registration; checkpoints still require supported built-in routes.
Use --source-password-env NAME and --pdf-password-env NAME for runtime secret
references. Saved jobs never contain password values. PowerShell runs the same
definition with Invoke-OfficeConversionJob -Path ./monthly.officeimojob.json.
Studio's local-folder workbench loads source-folder jobs that target PDF using
automatic route selection and have no password references. Use the CLI or
PowerShell for explicit-file lists, other targets, fixed conversion routes or
jobs with password environment-variable references.
Ordinary workflow batch keeps its aggregate JSON default. --format json
adds a versioned per-file report, bounded to 10,000 retained items and 16 MiB of
serialized item data, with an explicit truncation marker. --format ndjson
streams each item and a final summary. Saved-job execution defaults to the
versioned JSON report. Human diagnostics stay on stderr. A batch with no selected
conversions fails unless --allow-empty explicitly accepts that outcome; partial
failures and cancellation keep their failure/cancellation exit codes and retain
already published outputs.
If discovery or its file budget stops a run after earlier files complete, the
final report retains those item outcomes and includes summary.failureSummary.
The command fails even when no individual conversion failed; JSON and NDJSON
still include the terminal summary.
See the complete job examples for expected results and checkpoint retry instructions.
Retain a readable attempt independently of checkpoint state by choosing a new report path outside the input, output and checkpoint trees:
mkdir runs
officeimo workflow job run ./monthly.officeimojob.json --report ./runs/first.json
officeimo workflow job report ./runs/first.json
officeimo workflow job run ./monthly.officeimojob.json --retry-failed --report ./runs/retry.json
The report parent folder must exist. Existing report files are preserved. Each attempt records the saved definition's fingerprint, timing, aggregate outcome and bounded per-file results. Inspection never runs the job or opens its referenced files. A report left by an exited writer appears as interrupted; a live writer remains running. Reports describe past observations. The normal source, output and checkpoint checks still determine whether an artifact can be reused.
If report creation fails, conversion does not start. If final recording fails after conversions, the command reports the recording error and returns failure while retaining completed outputs and their conversion counts. Use a separate report filename for each attempt rather than replacing earlier evidence.
Common workflows
# Office documents to PDF
officeimo convert report.docx report.pdf
officeimo convert archive.doc archive.pdf
officeimo convert report.txt report.pdf --text-encoding utf-8 --tab-size 4
officeimo convert workbook.xlsx workbook.pdf
officeimo convert deck.pptx deck.pdf
# Draw pages to PDF, with source page sizes and explicit layer/loss choices
officeimo convert diagram.odg diagram.pdf
officeimo convert diagram.fodg diagram.pdf --diagram-layers screen
officeimo convert diagram.odg diagram.pdf --require-no-loss
# OpenDocument, email, EPUB and Visio to PDF
officeimo convert report.odt report.pdf
officeimo convert budget.ods budget.pdf
officeimo convert slides.odp slides.pdf
officeimo convert message.eml message.pdf
officeimo convert message.msg archive.pdf --text-only
officeimo convert book.epub book.pdf
officeimo convert diagram.vsdx diagram.pdf
# Markdown, HTML, RTF and ODT to Word, and Office to OpenDocument and back
officeimo convert notes.md notes.docx
officeimo convert page.html page.docx
officeimo convert letter.rtf letter.docx
officeimo convert report.docx report.odt
officeimo convert report.odt report.docx
officeimo convert workbook.xlsx workbook.ods
officeimo convert deck.pptx deck.odp
# DjVu scans to searchable PDF, using existing text layers
officeimo convert book.djvu book.pdf
officeimo convert scan.djv scan.pdf --require-no-loss
# Convert Apple ZIP files or local directory packages through shared workflows
officeimo convert document.pages document.docx
officeimo convert budget.numbers budget.xlsx
officeimo convert presentation.key presentation.pptx
officeimo convert document.pages document.pdf
# Supported documents to Markdown or JSON through OfficeIMO.Reader
officeimo convert workbook.xlsx workbook.md
officeimo convert report.docx report.json
# Extract to standard output or a file
officeimo read report.docx --format markdown
officeimo extract report.docx --format markdown --output report.md
# Return a compact JSON inspection result
officeimo inspect deck.pptx
# Inspect and convert tabular data without loading an editable workbook
officeimo tabular sheets workbook.xlsx
officeimo tabular schema workbook.xlsx --sheet Data
officeimo tabular convert input.csv output.xlsx
officeimo tabular convert workbook.xlsb output.tsv --sheet Data
officeimo tabular convert pipe-delimited.csv output.csv --delimiter '|' --output-delimiter ','
# Analyze embedded Word images without writing a file
officeimo workflow optimize-images input.docx --analyze
# Optimize a separate Word copy, or choose a .pdf output
officeimo workflow optimize-images input.docx --output optimized.docx --mode both --dpi 144 --quality 85
# Process an explicit batch; each output is independently staged and reopened
officeimo workflow optimize-images first.docx second.docx --output-directory optimized --format pdf --mode both
# Export selected PDF pages to validated images
officeimo workflow export-pages report.pdf --output .\report-pages --pages 1-3,last --format png
# Assemble an ordered PDF from files, folders, images, and ZIP archives
officeimo workflow assemble cover.png report.docx appendices .\attachments.zip --output complete.pdf
# Inspect print-sheet placement without requiring a platform printer driver
officeimo workflow print-plan complete.pdf --paper A4 --pages-per-sheet 2 --scale fit
# Inspect or assess provenance with versioned JSON output
officeimo provenance inspect report.docx
officeimo provenance assess page.html
# Remove selected, structurally valid carriers through the owning format package
officeimo provenance remove report.docx --output report.cleaned.docx
# Plan and apply source-bound PDF redactions through reusable JSON contracts
officeimo pdf redact providers --ocr-provider-assembly ./providers/MyOcr.Provider.dll
officeimo pdf redact plan contract.pdf --recipe redaction.recipe.json --evidence contract.plan.json
officeimo pdf redact apply contract.pdf --recipe redaction.recipe.json --decisions contract.decisions.json `
--output contract-redacted.pdf --evidence contract-redacted.evidence.json `
--ocr-provider my-provider --ocr-language en --ocr-option model=document
officeimo pdf redact batch --request redaction.batch.json
The positional destination is optional for supported Office and Draw inputs to PDF conversion. When omitted, the tool writes a sibling .pdf file. --output <path> remains available for scripts that prefer named options.
Markdown and JSON destinations are semantic Reader projections rather than fixed-layout renderings. They use the same handlers as officeimo reader read and support every input format reported by officeimo reader capabilities.
officeimo reader read accepts iWork directory bundles with .pages, .numbers, or .key extensions as individual documents. Folder discovery also keeps each bundle intact. Export files and asset directories must be outside the source bundle; reported size and content hashes describe the bounded captured package. These Reader outputs are semantic extraction, with the same rendering limits as other Reader routes.
Apple-to-OOXML and Apple-to-PDF conversion accept ZIP files and local directory packages and returns JSON with typed fidelity diagnostics, producer/projection facts, source snapshot SHA-256, coverage, and publication status. Defaults reject partial editable reconstruction and previews without known complete coverage. Use --iwork-mode auto|editable|visual, --allow-partial, --allow-incomplete-preview, and --normalize-worksheet-names only when those acceptance choices fit the task. --max-input-bytes and --max-output-bytes bound conversion. Directory-package checksums describe a private transport ZIP, identified by snapshotKind = DirectoryPackage. Root replacement and changes to file membership or content prevent publication. The destination must be outside the source package and separate from its members. Native permission-scoped directory intake remains outside this local-filesystem contract. PDF requires complete editable reconstruction and retains both source and PDF-stage evidence; partial output, previews, content exclusion and PDF-stage omissions or failures are rejected.
All convert destinations are protected from accidental replacement. Pass --force explicitly when an existing output file should be replaced.
OfficeIMO Document Tools MCPのよくある質問
OfficeIMO.Toolをインストールするにはどうすればよいですか?
NuGetから 'dotnet tool install --global OfficeIMO.Tool' コマンドを実行することで、グローバルにインストールできます。
スキャンされたPDFに対してOCRを実行できますか?
はい、Tesseractなどの信頼できるプロバイダーを指定することで、検索可能なOCRをサポートしています。ただし、OCRの実行ファイル自体は含まれていません。