MROffice is a fast-moving open-source office editor stack — about 1,800 GitHub stars within roughly twelve days of its November 10, 2026 creation date per the repo header — that targets builders who want Microsoft Office-like editing in the browser without shipping a closed SDK. The project separates AGPL editor source from a hosted embed and desktop shell that reads and writes .docx, .xlsx, and .pptx.
This post explains what shipped in the repo, how agents hook in via MCP, and where the license bites.
TL;DR #
| Question | Answer |
|---|---|
| License | AGPL-3.0 plusNOTICE.md attribution tomroffice.ai |
| Editors | Docs, sheets, slides, PDF, ink, code — packages under @mrnote/* |
| Agent path | mroffice-mcp or hosted** https://mcp.mroffice.ai/mcp** |
| Embed path | npx mroffice-embed init + server createSessionToken |
| Native Office files | Hosted embed or desktop , not pure OSS build |
| Try without clone | mroffice.ai live demo |
What is in the repository? #
Open and closed document editor stacks linked by a cable, illustrating MROffice embed versus AGPL self-host
Per the README:
Six editor packages
| Editor | Open formats | Notes |
|---|---|---|
| Documents | .mrdoc , HTML, Markdown, text |
Styles, tables, tracked changes UI |
| Spreadsheets | .mrsheet , CSV, TSV |
Cell math in browser; function formulas kept as text in OSS |
| Presentations | .mrslides |
Themes, transitions, animations preview |
| Read, annotate, print | Save returns unmodified bytes in OSS | |
| Handwriting | .mrink |
Pressure-sensitive ink |
| Code | Many languages | Runs JS/TS, Python, SQL, Lua, shell in browser |
Charts, SmartArt layout, and function evaluation (SUM, VLOOKUP, etc.) run in the proprietary MR Office engine inside the desktop app, per the README. OSS builds preserve those objects but do not recalc everything locally.
Apps and tooling
Three fanned document sheets, illustrating the six-editor office stack
apps/playground— browser demo atlocalhost:5178afternpm run build && npm run preview.apps/desktop— Electron shell; optionalMR Office component for full Office binaries.apps/mcp— source for**mroffice-mcp** .
How to run it locally #
From the README's quick path:
npm install
npm run fonts
npm run build
npm run preview
npm run dev serves the same playground for development. npm run smoke checks a build.
Fonts: npm run fonts installs open substitutes for Office fonts — required before a faithful preview.
MCP for AI agents #
MCP connectors linking tools to an agent workflow
The README documents two agent entry points:
- Hosted MCP —
https://mcp.mroffice.ai/mcp(sign in with an MR Office account, no API key in the quick start). - Local MCP —
npx -y mroffice-mcpon a developer machine.
That pattern matches how explainx.ai covers other document agent bridges — see Univer's facade API and AWS agent skills for caching. MROffice's pitch is real editor sessions, not headless conversion only.
When to pick MCP vs npm packages
| Approach | Best for |
|---|---|
| mroffice-mcp | Agent frameworks that already speak MCP (Claude Desktop, custom hosts) |
mroffice-docs npm |
React apps embedding a single editor component |
mroffice-embed |
SaaS products that need .docx without AGPL on your core app |
Embed vs AGPL self-host #
Hosted embed (recommended in README)
Your server mints a short-lived session token with createSessionToken from mroffice-embed/server. The browser calls open() from mroffice-embed. Files round-trip through signed callbacks.
Free tier limits quoted in README (November 2026): 1,000 sessions/month on localhost, 100 on custom domains, up to 2 apps.
Because MR Office hosts the editor, your product is not automatically AGPL when you use the hosted service — the README explicitly contrasts this with shipping modified AGPL sources yourself.
Self-host AGPL editors
If you modify and serve the six editors over a network, AGPL-3.0 requires offering complete corresponding source to users, plus NOTICE.md branding rules (keep MR Office attribution and link).
A commercial license from support@mr-note.com is the escape hatch if you need proprietary distribution.
npm packages #
Install per editor, for example:
npm i mroffice-docs mroffice-core
Sibling packages: mroffice-sheets, mroffice-slides, mroffice-pdf, mroffice-ink, mroffice-code. Each README documents React embedding.
compare to Gamma agent slides when your agents only need deck generation, not Excel-grade grids.
OAuth and developer console #
MR Office also acts as an OAuth 2.1 authorization server (PKCE, dynamic registration). That is separate from MCP but useful if your product wants Sign in with MR Office instead of storing Office credentials.
Developer docs live at mroffice.ai developers per the README (sign-in required).
Architecture: what is open vs closed #
The README's diagram is explicit:
- AGPL block:
@mrnote/core, six editors, playground, desktop** shell source** , and MCP server source. - Non-OSS component:**MR Office component that implementsWord/Excel/PowerPoint/PDF write-back** and advanced engine features —free to use butnot open source .
That split is why the project can be trending on GitHub without giving away the Office compatibility layer. It mirrors how OnlyOffice-style products separate community document editors from document server builds.
Session flow for embed
- User authenticates on your app .
- Your backend calls
createSessionTokenwithappId,secretKey, file metadata, and user id. - Frontend
open()loads the hosted editor with the token. - On save, MR Office POSTs to your signed callback with the updated file.
This is closer to Figma embed or Google Picker than to shipping a static iframe of a bundled WASM build. Agents using MCP skip your iframe but still rely on MR Office's hosted runtime unless you run mroffice-mcp locally with a desktop install.
Package map for monorepo readers #
| Path | Role |
|---|---|
packages/docs |
Document editor React component |
packages/sheets |
Spreadsheet grid |
packages/slides |
Deck editor |
packages/pdf |
Viewer and markup |
packages/ink |
Handwriting canvas |
packages/code |
Lightweight IDE surface |
packages/core |
Shared UI and model code |
fonts/office-pack |
Open font substitutes |
llms.txt |
Machine-readable project summary for agents |
The repo ships llms.txt, signaling that maintainers expect coding agents to read the tree — similar spirit to AGENTS.md in other trending repos.
Spreadsheet semantics for agents #
OSS spreadsheets evaluate arithmetic between cells (=A1*B1+10) but keep function formulas as written without full Excel recalc. Agents that overwrite cells can therefore leave stale function results until the proprietary engine runs.
Mitigation patterns:
- Use hosted embed when agents must returncustomer-grade Excel .
- For internal dashboards, export CSV after agent passes and re-import through a pipeline you control.
- Log before/after cell JSON when agents touch sheets — auditability matters forfinance agent posts .
Presentation and PDF surfaces #
Slides support eight themes, master/layout views, and animation preview in OSS. PDF mode supports highlight, underline, strikethrough, squiggly, and comments but does not write annotations back into the PDF bytes on OSS save paths.
For teams comparing Gamma-generated decks vs live slide edits, use Gamma 5 coverage for generation, MROffice for pixel-level deck surgery.
Desktop vs browser-only #
npm run desktop launches MR Office Editors shell. Without the proprietary component, desktop mode still opens .mrdoc / .mrsheet / .mrslides and PDFs. With the component from Releases, it becomes the full MR Office desktop app with AI features and native Office binaries.
Windows and macOS installers are advertised at mroffice.ai for teams that need offline access — relevant when your agent must edit on an air-gapped machine and sync later.
Star velocity and maintenance risk #
~1,755 stars in roughly twelve days (per candidate feed) puts MROffice in the same attention bucket as other agent-tooling repos explainx.ai covered this month. High stars do not guarantee:
- Long-term maintenance
- Stable MCP schemas
- Pen-tested embed callbacks
Pin commit SHAs in production integrations and run npm run smoke in CI after upgrades.
Comparison table: MROffice vs alternatives #
| Product | License / host | Native .docx |
Agent hook |
|---|---|---|---|
| MROffice OSS | AGPL self-host | No | npm + optional MCP |
| MROffice embed | Hosted commercial | Yes | Same MCP + tokens |
| Univer | Apache-2.0 facade | Partial via integrations | Facade API |
| Google Docs API | SaaS | Yes | REST, not MCP-native |
| Microsoft 365 Copilot | SaaS | Yes | Microsoft graph stack |
Pick two layers: one generation tool (LLM) and one faithful editor (MROffice embed or desktop) when contracts require Office file types.
What people are asking on Hacker News #
The repo's HN thread (low score, early stage) will matter less than agent builders trying embed limits. Common questions map to:
Is this AGPL contamination for my SaaS?
Use hosted embed if you do not want copyleft on your core codebase. Self-host only with legal review.
Can agents replace LibreOffice headless?
Different tradeoff. MROffice optimizes WYSIWYG and human+agent co-editing. Headless LibreOffice suits batch conversion; see Libreboot anti-AI policy discourse for another angle on OSS purity vs agents.
How is this different from Univer?
Univer focuses on facade APIs for spreadsheets and docs your agents already control. MROffice adds MCP, PDF ink, and a commercial Office-IO layer. Many teams will prototype on Univer and pilot MROffice embed when .docx fidelity matters.
Security and data handling #
- Session tokens must stay server-side; README shows
mro_sk_secrets only on the server. - Callbacks are signed — treat forged save URLs like any webhook auth bug.
- AGPL does not imply security audit; run your own review before customer PII.
For agent misuse patterns, see OpenRouter support-email read claims as a reminder that tools that read documents need scope limits.
Limitations (honest) #
- Star velocity ≠ production maturity — the repo is only weeks old; expect API churn.
- No native
.docxin OSS — demo videos may show desktop/hosted features; label your integration correctly. - Function recalc in sheets requiresdesktop/proprietary engine for full Excel parity.
Bottom line #
MROffice is worth a look if you build agents that must edit real office artifacts and you can accept AGPL or paid embed. Clone for UI experiments; buy or embed for Word/Excel fidelity.
Related reading #
Repository layout and license text are accurate as of November 22, 2026 per GitHub README.