{"slug": "mroffice-open-source-office-editors-mcp-tools-and-what-agpl-means-for-agents", "title": "MROffice: Open-Source Office Editors, MCP Tools, and What AGPL Means for Agents", "summary": "MROffice, an open-source office editor stack created on November 10, 2026, reached about 1,800 GitHub stars in roughly twelve days, according to the project's repository header. The project ships six editor packages under the @mrnote/* scope (documents, spreadsheets, presentations, PDF, handwriting and code) under AGPL-3.0 with a NOTICE.md attribution to mroffice.ai, and exposes AI agents to real editor sessions through a hosted MCP endpoint at https://mcp.mroffice.ai/mcp or the local `npx -y mroffice-mcp` package. Native .docx, .xlsx and .pptx read/write, plus charts, SmartArt layout and function evaluation such as SUM and VLOOKUP, run only in the proprietary MR Office engine inside the hosted embed or desktop app, not in the pure open-source build.", "body_md": "**[MROffice](https://github.com/XinaTian/MROffice?ref=explainx)** 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**.\n\nThis post explains **what shipped in the repo**, **how agents hook in via MCP**, and **where the license bites**.\n\n## TL;DR\n\n| Question | Answer | \n|---|---|\n| License | **AGPL-3.0** plus**NOTICE.md** attribution to[mroffice.ai](https://mroffice.ai/?ref=explainx) | \n| Editors | Docs, sheets, slides, PDF, ink, code — packages under `@mrnote/*` | \n| Agent path | **`mroffice-mcp`** or hosted**` https://mcp.mroffice.ai/mcp`** | \n| Embed path | **`npx mroffice-embed init`** + server` createSessionToken` | \n| Native Office files | **Hosted embed or desktop** , not pure OSS build | \n| Try without clone | [mroffice.ai](https://mroffice.ai/?ref=explainx) live demo | \n\n## What is in the repository?\n\nOpen and closed document editor stacks linked by a cable, illustrating MROffice embed versus AGPL self-host\n\nPer the [README](https://github.com/XinaTian/MROffice?ref=explainx):\n\n### Six editor packages\n\n| Editor | Open formats | Notes | \n|---|---|---|\n| **Documents** | `.mrdoc` , HTML, Markdown, text | Styles, tables, tracked changes UI | \n| **Spreadsheets** | `.mrsheet` , CSV, TSV | Cell math in browser; **function formulas kept as text** in OSS | \n| **Presentations** | `.mrslides` | Themes, transitions, animations preview | \n| **PDF** | Read, annotate, print | Save returns **unmodified bytes** in OSS | \n| **Handwriting** | `.mrink` | Pressure-sensitive ink | \n| **Code** | Many languages | Runs JS/TS, Python, SQL, Lua, shell in browser | \n\n**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.\n\n### Apps and tooling\n\nThree fanned document sheets, illustrating the six-editor office stack\n\n- **`apps/playground`** — browser demo at` localhost:5178` after`npm run build && npm run preview` .\n- **`apps/desktop`** — Electron shell; optional**MR Office component** for full Office binaries.\n- **`apps/mcp`** — source for**` mroffice-mcp`** .\n\n## How to run it locally\n\nFrom the README's quick path:\n\n```\nnpm install\nnpm run fonts\nnpm run build\nnpm run preview\n```\n\n`npm run dev` serves the same playground for development. `npm run smoke` checks a build.\n\n**Fonts:** `npm run fonts` installs open substitutes for Office fonts — required before a faithful preview.\n\n## MCP for AI agents\n\nMCP connectors linking tools to an agent workflow\n\nThe README documents two agent entry points:\n\n1. **Hosted MCP** —`https://mcp.mroffice.ai/mcp` (sign in with an MR Office account, no API key in the quick start).\n2. **Local MCP** —`npx -y mroffice-mcp` on a developer machine.\n\nThat pattern matches how explainx.ai covers other **document agent bridges** — see [Univer's facade API](https://explainx.ai/blog/univer-office-sdk-open-source-spreadsheets-agents-facade-api-2026) and [AWS agent skills for caching](https://explainx.ai/blog/aws-distributed-kv-caching-agent-skill-elasticache-november-2026). MROffice's pitch is **real editor sessions**, not headless conversion only.\n\n### When to pick MCP vs npm packages\n\n| Approach | Best for | \n|---|---|\n| **mroffice-mcp** | Agent frameworks that already speak **MCP** (Claude Desktop, custom hosts) | \n| **`mroffice-docs` npm** | React apps embedding a single editor component | \n| **`mroffice-embed`** | SaaS products that need **.docx** without AGPL on your core app | \n\n## Embed vs AGPL self-host\n\n### Hosted embed (recommended in README)\n\nYour 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**.\n\nFree tier limits quoted in README (November 2026): **1,000 sessions/month on localhost**, **100 on custom domains**, up to **2 apps**.\n\nBecause 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.\n\n### Self-host AGPL editors\n\nIf 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).\n\nA **commercial license** from `support@mr-note.com` is the escape hatch if you need proprietary distribution.\n\n## npm packages\n\nInstall per editor, for example:\n\n```\nnpm i mroffice-docs mroffice-core\n```\n\nSibling packages: **`mroffice-sheets`**, **` mroffice-slides`**, **` mroffice-pdf`**, **` mroffice-ink`**, **` mroffice-code`**. Each README documents React embedding.\n\ncompare to **[Gamma agent slides](https://explainx.ai/blog/gamma-5-agent-driven-presentations-ai-smell-what-changed-2026)** when your agents only need **deck generation**, not **Excel-grade grids**.\n\n## OAuth and developer console\n\nMR 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.\n\nDeveloper docs live at **[mroffice.ai developers](https://mroffice.ai/?ref=explainx)** per the README (sign-in required).\n\n## Architecture: what is open vs closed\n\nThe README's diagram is explicit:\n\n- **AGPL block:**`@mrnote/core` , six editors, playground, desktop** shell source** , and MCP server source.\n- **Non-OSS component:****MR Office component** that implements**Word/Excel/PowerPoint/PDF write-back** and advanced engine features —**free to use** but**not open source** .\n\nThat split is why the project can be **trending on GitHub** without giving away the **Office compatibility layer**. It mirrors how **[OnlyOffice](https://explainx.ai/blog/agentes-chat-open-source-self-hosted-slack-alternative-ai-agents-mcp-agpl-github-trending-2026)**-style products separate **community document editors** from **document server** builds.\n\n### Session flow for embed\n\n1. User authenticates on **your app** .\n2. Your backend calls **`createSessionToken`** with` appId` ,`secretKey` , file metadata, and user id.\n3. Frontend **`open()`** loads the hosted editor with the token.\n4. On save, MR Office POSTs to your **signed callback** with the updated file.\n\nThis 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.\n\n## Package map for monorepo readers\n\n| Path | Role | \n|---|---|\n| `packages/docs` | Document editor React component | \n| `packages/sheets` | Spreadsheet grid | \n| `packages/slides` | Deck editor | \n| `packages/pdf` | Viewer and markup | \n| `packages/ink` | Handwriting canvas | \n| `packages/code` | Lightweight IDE surface | \n| `packages/core` | Shared UI and model code | \n| `fonts/office-pack` | Open font substitutes | \n| `llms.txt` | Machine-readable project summary for agents | \n\nThe repo ships **`llms.txt`**, signaling that maintainers expect **coding agents** to read the tree — similar spirit to **`AGENTS.md`** in other trending repos.\n\n## Spreadsheet semantics for agents\n\nOSS 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.\n\n**Mitigation patterns:**\n\n- Use **hosted embed** when agents must return**customer-grade Excel** .\n- For internal dashboards, export **CSV** after agent passes and re-import through a pipeline you control.\n- Log **before/after cell JSON** when agents touch sheets — auditability matters for[finance agent posts](https://explainx.ai/blog/sakana-applied-research-lab-cofe-finance-agents-november-2026) .\n\n## Presentation and PDF surfaces\n\nSlides 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.\n\nFor teams comparing **Gamma-generated decks** vs **live slide edits**, use [Gamma 5 coverage](https://explainx.ai/blog/gamma-5-agent-driven-presentations-ai-smell-what-changed-2026) for **generation**, MROffice for **pixel-level deck surgery**.\n\n## Desktop vs browser-only\n\n`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.\n\nWindows 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.\n\n## Star velocity and maintenance risk\n\n**~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:\n\n- Long-term maintenance\n- Stable MCP schemas\n- Pen-tested embed callbacks\n\nPin **commit SHAs** in production integrations and run **`npm run smoke`** in CI after upgrades.\n\n## Comparison table: MROffice vs alternatives\n\n| Product | License / host | Native `.docx` | Agent hook | \n|---|---|---|---|\n| **MROffice OSS** | AGPL self-host | No | npm + optional MCP | \n| **MROffice embed** | Hosted commercial | Yes | Same MCP + tokens | \n| **Univer** | Apache-2.0 facade | Partial via integrations | Facade API | \n| **Google Docs API** | SaaS | Yes | REST, not MCP-native | \n| **Microsoft 365 Copilot** | SaaS | Yes | Microsoft graph stack | \n\nPick **two layers**: one **generation** tool (LLM) and one **faithful editor** (MROffice embed or desktop) when contracts require **Office file types**.\n\n## What people are asking on Hacker News\n\nThe repo's HN thread (low score, early stage) will matter less than **agent builders trying embed limits**. Common questions map to:\n\n### Is this AGPL contamination for my SaaS?\n\n**Use hosted embed** if you do not want copyleft on your core codebase. **Self-host** only with legal review.\n\n### Can agents replace LibreOffice headless?\n\n**Different tradeoff.** MROffice optimizes **WYSIWYG** and **human+agent co-editing**. Headless LibreOffice suits batch conversion; see [Libreboot anti-AI policy discourse](https://explainx.ai/blog/libreboot-drops-anti-ai-policy-slop-reduction-november-2026) for another angle on **OSS purity vs agents**.\n\n### How is this different from Univer?\n\nUniver 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.\n\n## Security and data handling\n\n- **Session tokens** must stay server-side; README shows`mro_sk_` secrets only on the server.\n- **Callbacks** are signed — treat forged save URLs like any webhook auth bug.\n- **AGPL** does not imply security audit; run your own review before customer PII.\n\nFor agent misuse patterns, see [OpenRouter support-email read claims](https://explainx.ai/blog/openrouter-minimax-prompts-may-have-been-read-customer-email-november-2026) as a reminder that **tools that read documents** need **scope limits**.\n\n## Limitations (honest)\n\n- **Star velocity ≠ production maturity** — the repo is only weeks old; expect API churn.\n- **No native `.docx` in OSS** — demo videos may show desktop/hosted features; label your integration correctly.\n- **Function recalc** in sheets requires**desktop/proprietary engine** for full Excel parity.\n\n## Bottom line\n\n**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**.\n\n## Related reading\n\n*Repository layout and license text are accurate as of November 22, 2026 per GitHub README.*", "url": "https://wpnews.pro/news/mroffice-open-source-office-editors-mcp-tools-and-what-agpl-means-for-agents", "canonical_source": "https://explainx.ai/blog/mroffice-open-source-office-editors-mcp-agents-agpl-november-2026?utm_source=rss&utm_medium=feed&utm_campaign=blog", "published_at": "2026-11-22 00:00:00+00:00", "updated_at": "2026-11-22 06:42:09.545962+00:00", "lang": "en", "topics": ["ai-agents", "agent-protocols", "developer-tools", "ai-tools"], "entities": ["MROffice", "XinaTian", "mroffice.ai", "mroffice-mcp", "mroffice-embed", "MR Office", "Claude Desktop", "GitHub"], "also_reported_by": [], "takeaway": "MROffice's AGPL-3.0 editors expose agent access via the hosted MCP endpoint https://mcp.mroffice.ai/mcp or local `npx -y mroffice-mcp`, but native .docx/.xlsx/.pptx handling and formula evaluation require the proprietary MR Office engine in the hosted embed or desktop app.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/mroffice-open-source-office-editors-mcp-tools-and-what-agpl-means-for-agents", "markdown": "https://wpnews.pro/news/mroffice-open-source-office-editors-mcp-tools-and-what-agpl-means-for-agents.md", "text": "https://wpnews.pro/news/mroffice-open-source-office-editors-mcp-tools-and-what-agpl-means-for-agents.txt", "jsonld": "https://wpnews.pro/news/mroffice-open-source-office-editors-mcp-tools-and-what-agpl-means-for-agents.jsonld"}}