OfficeCLI

Open source alternative to Aspose.Total and MESCIUS Document Solutions

32.8K stars
Apache-2.0
Active this week
Last commit 1 day ago

Last verified Oct 30, 2026

Automate Word, Excel, and PowerPoint from the command line with a single binary that needs no Office installation, built for AI agents and developers.

Visit website GitHub32.8K

Read the full breakdownWho it is for, how it works, trade-offs, the quick start and the FAQ

who it's for

Who OfficeCLI is for#

AI engineers wiring coding agents into document workflows

OfficeCLI installs its skill file into AI coding agents automatically, so Claude Code, Cursor, or Windsurf can create, read, and edit .docx, .xlsx, and .pptx files on the engineer's behalf. The built-in rendering engine gives the agent PNG output to verify that generated content looks correct before delivery.

Skip if:

If your agent only needs to read structured data (JSON, CSV) and never touches Office formats, a lighter-weight file parsing library covers the need without the OfficeCLI binary.

Developers building CI/CD document generation pipelines

Report generation, test-result formatting, and template population all map to single `officecli` commands that run in Docker or any Linux CI runner. The tool returns structured JSON output so downstream steps can consume results without parsing binary formats.

Skip if:

If your pipeline outputs PDF only and never generates editable Office files, a PDF-native library is simpler and does not need OfficeCLI.

Teams doing batch document processing and validation

Bulk find-and-replace, style updates, and content validation across a directory of .docx or .xlsx files can be scripted with standard shell tools and `officecli` commands. The XPath-style selectors make it straightforward to target specific elements across many files without writing format-parsing code.

Skip if:

Teams whose documents live entirely in Google Workspace or web-native editors will not benefit; OfficeCLI works with local or network-accessible .docx/.xlsx/.pptx files only.

Developers adding headless Office automation to containerized services

Because the binary is self-contained and Office is not required, OfficeCLI runs inside a minimal Docker container with no additional setup beyond downloading the binary. This makes it practical for cloud-hosted services that generate or process Office documents on demand.

Skip if:

If your service runs in a WebAssembly or browser environment, the native binary cannot execute there. Web-based document processing requires a different approach.

the problem

The problem it solves#

Automating Word, Excel, and PowerPoint files programmatically has always required either a full Microsoft Office installation, a paid SDK library with per-developer licensing, or brittle third-party libraries maintained in isolation. Commercial SDKs like Aspose.Total and MESCIUS Document Solutions charge per-developer licensing fees and provide no CLI interface, forcing developers to write glue code in whatever language the SDK supports.

The deeper issue for AI agents is that document manipulation APIs work on the underlying XML structure but provide no rendering output. An agent can add a slide, set a font size, or insert a chart, but it cannot verify that the result looks correct. A title might overflow, shapes might overlap, or a chart might render blank, all undetectable without a human opening the file. Document-producing AI agents end up operating without a feedback loop to catch layout or formatting failures.

how OfficeCLI solves it

How it solves it#

Built-in HTML rendering engine for AI document vision

Converts any .docx, .xlsx, or .pptx file into a standalone HTML file or per-page PNG screenshots using a from-scratch rendering engine embedded in the binary. `officecli view deck.pptx screenshot` produces PNG output ready to feed into a multimodal model with no server or display required. The `watch` command opens a live-reloading browser preview at localhost:26315 so every edit immediately updates the rendered view.

Single self-contained binary with embedded .NET runtime

Ships as a self-contained binary for macOS (Apple Silicon and Intel), Linux (x64 and ARM64), and Windows (x64 and ARM64). The .NET runtime is bundled inside, so there are no dependencies to install and no runtime version conflicts to manage. The same binary runs on a local machine, in a Docker container, or in a CI environment.

Full read, write, and create support across all three Office formats

Handles Word (.docx), Excel (.xlsx), and PowerPoint (.pptx) with create, read, and modify operations across all three. Excel support includes 350+ built-in functions with auto-evaluation, pivot tables, conditional formatting, and CSV/TSV import. PowerPoint support covers animations, transitions, 3D models (.glb), and mermaid diagram import as native editable shapes.

AI agent skill file and MCP server integration

Running `officecli install` automatically places a skill file into Claude Code, Cursor, Windsurf, GitHub Copilot, and other coding agents it detects. The skill file teaches the agent all available commands so it can create and edit Office documents immediately. OfficeCLI also ships as an MCP server for direct tool-protocol integration without a CLI intermediary.

XPath-style element selectors for precise targeting

Every element in a document is addressable with an XPath-like path: `/slide[1]/shape[@name=Foo]` for a named PowerPoint shape, `row[Salary>5000 and Region=EMEA]` for Excel rows matching multiple conditions, or `/revision[@author=Alice]` for tracked changes by a specific author. This gives scripts and agents a predictable way to get, set, add, or remove any element.

Word internationalisation with RTL and per-script font support

Word document support includes full i18n and RTL coverage: per-script font slots, BCP-47 language tags (lang.latin/ea/cs), locale-aware page numbering for Hindi, Arabic, Thai, and CJK scripts, and `create --locale ar-SA` to auto-enable RTL. Direction cascades through paragraph, run, section, table, style, header, footer, and document defaults.

strengths · trade-offs

Strengths and trade-offs#

Strengths

Apache-2.0 license with no per-developer licensing feesThe Apache-2.0 license permits commercial use on any number of machines without per-developer or per-server fees. Aspose.Total and MESCIUS Document Solutions both charge commercial licensing fees that accumulate with team size. OfficeCLI has 32,763 GitHub stars, indicating the approach has found broad validation in the developer community.
No Microsoft Office dependency at any stageThe binary needs nothing from the host system: no Microsoft Office, no COM automation, no .NET SDK, and no additional system libraries. This makes it viable in minimal Docker containers, serverless functions, or CI runners where installing Office is not possible. The .NET runtime ships inside the binary.
CLI-first interface maps directly to agent and script useEvery operation is a single command: `officecli create deck.pptx`, `officecli add deck.pptx / --type slide --prop title="Q4 Report"`. The command structure matches what an AI agent would output, and the tool returns structured JSON for programmatic consumption, keeping the feedback loop tight without custom glue code.
Active development: 6,262 commits and multilingual documentationCreated in March 2026 and last pushed on October 28, 2026, OfficeCLI has accumulated 6,262 commits and 2,224 forks. The project has 29 open issues as of October 2026, indicating active triage. README translations are available in English, Chinese, Japanese, and Korean.

Trade-offs

-Larger binary footprint due to embedded .NET runtimeBecause the .NET runtime ships inside the binary, the download is larger than a pure Python or Node.js library for Office file manipulation. This is a deliberate trade for zero runtime management, but teams with strict artifact size constraints should account for it in their Docker image or CI pipeline.
-29 open issues on a project under eight months oldOfficeCLI was created in March 2026 and has 29 open issues as of October 2026. For a project at this stage of adoption that count is manageable, but teams with strict stability requirements should review the open issue list before building a production dependency on it.
-No graphical interface: CLI and agent use onlyOfficeCLI itself has no graphical interface. For teams that need a point-and-click experience, the AionUi companion app is the documented path, but it is a separate project with its own setup. If the workflow is entirely GUI-based, OfficeCLI is not the right fit on its own.

versus alternatives

OfficeCLI vs alternatives#

OfficeCLI vs Aspose.Total

Aspose.Total is a commercial SDK suite for reading and writing Office documents across multiple programming languages. OfficeCLI and Aspose.Total overlap in their ability to create, read, and modify .docx, .xlsx, and .pptx files without requiring Microsoft Office.

Feature	OfficeCLI	Aspose.Total
License	Apache-2.0	Proprietary
Pricing	Free	Commercial per-developer license
Interface	CLI and MCP server	SDK library (multiple languages)
Self-hosting	Yes, single binary	SDK embedded in your application
Rendering engine	Built-in HTML and PNG	Not included
AI agent integration	Native skill file and MCP	Not included

OfficeCLI is the better choice when you need a CLI-first interface, headless document rendering for visual verification, or a zero-licensing-fee deployment. Teams building AI-agent workflows will find the built-in rendering engine and MCP server integration directly useful in ways Aspose.Total does not cover.

Aspose.Total is worth considering when your codebase already uses an SDK integration pattern, when you need format support beyond .docx/.xlsx/.pptx (PDF, email, CAD), or when your team's licensing relationship with Aspose is already established.

OfficeCLI vs MESCIUS Document Solutions

MESCIUS Document Solutions is a commercial SDK library for Office file manipulation in .NET applications. It shares OfficeCLI's .NET foundation but targets developers embedding document processing into applications rather than running it from a CLI or agent context.

Feature	OfficeCLI	MESCIUS Document Solutions
License	Apache-2.0	Proprietary
Pricing	Free	Commercial per-developer license
Interface	CLI and MCP server	SDK library (.NET)
Self-hosting	Yes, single binary	SDK embedded in your application
Rendering engine	Built-in HTML and PNG	Not included
CI/CD pipeline use	Native via single command	Requires custom integration code

OfficeCLI fits better when the goal is CLI-driven automation, CI/CD pipeline integration, or equipping an AI agent to generate and inspect Office documents. The Apache-2.0 license removes per-developer cost considerations.

MESCIUS Document Solutions is better suited to .NET application developers who want a polished SDK for embedding Office document generation directly into a desktop or web application, with commercial support and API patterns they likely already know.

install · quick start

Quick start#

bash

Install OfficeCLI with the one-line setup script or a package manager; the binary embeds the .NET runtime and requires no additional dependencies.

```bash
curl -fsSL https://raw.githubusercontent.com/iOfficeAI/OfficeCLI/main/install.sh | bash
brew install officecli
npm install -g @officecli/officecli
```

tech stack · detected from GitHub

What it's built on#

Languages: C#JavaScript

frequently asked

FAQ#

Does OfficeCLI require Microsoft Office to be installed?

No. OfficeCLI ships as a self-contained binary with the .NET runtime embedded inside. It has no dependency on Microsoft Office, COM automation, or any Office runtime. The same binary runs on macOS, Linux, and Windows without any additional setup.

What license does OfficeCLI use?

OfficeCLI is licensed under Apache-2.0, which permits commercial use, modification, and distribution without per-developer fees. You can run it on any number of machines, use it in commercial products, and modify the source without restriction, as long as you include the license notice.

How does OfficeCLI integrate with AI coding agents like Claude Code?

Running officecli install after downloading the binary automatically installs the OfficeCLI skill file into every AI coding agent it detects, including Claude Code, Cursor, Windsurf, and GitHub Copilot. The skill file teaches the agent all available commands. For agents without a desktop installation, pasting curl -fsSL https://officecli.ai/SKILL.md into the agent chat triggers an automatic install and skill registration.

Can OfficeCLI run in Docker or CI/CD pipelines?

Yes. The binary is self-contained and runs on Linux x64 and ARM64, so it installs and executes inside standard Docker containers using the one-line install script. No Office installation is needed in the container. Teams typically download the platform-specific binary from GitHub Releases and add it to their image, or run the install script as part of the container build.

How do I preview a document without opening Microsoft Office?

officecli view deck.pptx html generates a standalone HTML file with all assets inlined that opens in any browser. officecli view deck.pptx screenshot produces per-page PNG files suitable for visual review or multimodal AI input. The officecli watch deck.pptx command starts a local HTTP server at port 26315 that auto-refreshes as you edit the document in another terminal.

also worth a look

Similar open-source tools#

rakazo

Featured

Alternative toGrok Bot

AI teammates you own: your keys, your model, your machine.

6,242 GitHub stars
Licence Apache-2.0

Zephium

Alternative toArc

Rust browser on your system's own engine, with an AI Work canvas

866 GitHub stars
Licence MPL-2.0

Parrotflow

Alternative toWispr Flow

Scriptable local dictation with rules, screen context, and vocabulary.

22 GitHub stars
Licence GPL-3.0

Cherry Studio

Alternative toTypingMind

Local-first AI workstation with agents and multi-model chat.

53,049 GitHub stars
Licence AGPL-3.0

AutoCua

Alternative toOpenAI Operator

Computer-use agent: desktop, browser, terminal, and iOS automation.

666 GitHub stars
Licence MIT

Voice Assistant

Alternative toSuperwhisper

Voice interface for Claude Code with local Whisper and spoken answers

2 GitHub stars
Licence MIT

by category

Open source tools in these categories#

429

12,826 GitHub stars
Licence AGPL-3.0
#Email

Omnara

Alternative toClaude Managed Agents

Open-source agent deployment API. Self-host or use Omnara Cloud.

3,296 GitHub stars
Licence Apache-2.0
#AI Agents

rakazo

Alternative toGrok Bot

AI teammates you own: your keys, your model, your machine.

6,242 GitHub stars
Licence Apache-2.0
#AI Agents

Advertise your product

The projects we add and every new guide. Free, unsubscribe any time.

Find open source alternatives to paid software

OfficeCLI vs Aspose.Total

Feature	OfficeCLI	Aspose.Total
License	Apache-2.0	Proprietary
Pricing	Free	Commercial per-developer license
Interface	CLI and MCP server	SDK library (multiple languages)
Self-hosting	Yes, single binary	SDK embedded in your application
Rendering engine	Built-in HTML and PNG	Not included
AI agent integration	Native skill file and MCP	Not included

OfficeCLI vs MESCIUS Document Solutions

Feature	OfficeCLI	MESCIUS Document Solutions
License	Apache-2.0	Proprietary
Pricing	Free	Commercial per-developer license
Interface	CLI and MCP server	SDK library (.NET)
Self-hosting	Yes, single binary	SDK embedded in your application
Rendering engine	Built-in HTML and PNG	Not included
CI/CD pipeline use	Native via single command	Requires custom integration code

Who OfficeCLI is for#

AI engineers wiring coding agents into document workflows

Skip if:

Developers building CI/CD document generation pipelines

Skip if:

Teams doing batch document processing and validation

Skip if:

Developers adding headless Office automation to containerized services

Skip if:

The problem it solves#

How it solves it#

Built-in HTML rendering engine for AI document vision

Single self-contained binary with embedded .NET runtime

Full read, write, and create support across all three Office formats

AI agent skill file and MCP server integration

XPath-style element selectors for precise targeting

Word internationalisation with RTL and per-script font support

Strengths and trade-offs#

Strengths

Trade-offs

OfficeCLI vs alternatives#

OfficeCLI vs Aspose.Total

OfficeCLI vs MESCIUS Document Solutions

Quick start#

What it's built on#

FAQ#

Similar open-source tools#

Open source tools in these categories#

AI & Machine Learning

Developer Tools

Business & Productivity

Find open source alternatives to paid software

Who OfficeCLI is for#

AI engineers wiring coding agents into document workflows

Skip if:

Developers building CI/CD document generation pipelines

Skip if:

Teams doing batch document processing and validation

Skip if:

Developers adding headless Office automation to containerized services

Skip if:

The problem it solves#

How it solves it#

Built-in HTML rendering engine for AI document vision

Single self-contained binary with embedded .NET runtime

Full read, write, and create support across all three Office formats

AI agent skill file and MCP server integration

XPath-style element selectors for precise targeting

Word internationalisation with RTL and per-script font support

Strengths and trade-offs#

Strengths

Trade-offs

OfficeCLI vs alternatives#

OfficeCLI vs Aspose.Total

OfficeCLI vs MESCIUS Document Solutions

Quick start#

What it's built on#

FAQ#

Similar open-source tools#

Open source tools in these categories#

AI & Machine Learning

Developer Tools

Business & Productivity

Find open source alternatives to paid software