Skip to content

MR Office open-sources six browser editors under AGPL-3.0

The GitHub repository publishes the source of MR Office's document, spreadsheet, presentation, PDF, handwriting and code editors, while Word, Excel and PowerPoint file handling stays in the commercial product.

Draftship Editorial4 min read

MR Office, a product that bundles document, spreadsheet, presentation, PDF, handwriting and code editors in the browser, has published the source of those six editors on GitHub. The repository, XinaTian/MROffice, was created on 2026-11-10 and had 1,410 stars and 158 forks as of 2026-11-21, 11 days later. It is mainly TypeScript and licensed AGPL-3.0. The MR Office open-source editors can be built, run and embedded, but the announcement is explicit that they are editors, not a complete office suite.

What the six editors do

The documents editor is a paged word processor with styles, tables, headers and footers, columns, tracked changes, comments and pen ink, saving its own .mrdoc format and opening HTML, Markdown and plain text. Spreadsheets handle cells, number formats, conditional formatting, sorting, filtering, frozen panes and multiple sheets, saving .mrsheet and reading and writing CSV and TSV. Presentations cover layouts, a slide master, transitions and animations with preview, and a slide show, in .mrslides. PDF support covers reading, search, presenting, printing and markup with notes. The handwriting editor saves .mrink with pressure-sensitive pens and a lasso, and the code editor offers syntax highlighting, an outline and find and replace, with JavaScript, TypeScript, Python, SQL, Lua and shell running in the browser.

What the licence does not cover

Word, Excel and PowerPoint files (.docx, .xlsx, .pptx) are not part of the open-source editors. According to the announcement, opening and saving those formats, recalculating formulas that use functions such as SUM or VLOOKUP, drawing charts and laying out SmartArt all run in MR Office's own engine, in the desktop app. The open-source editors keep the formulas, charts and SmartArt a file already holds and display SmartArt as it was saved. In the desktop build, the Electron shell is AGPL source, while the component that adds Office file support is compiled, free to use and not open source.

Three ways to use the editors

The recommended route is the hosted embed. A developer runs npx mroffice-embed init or creates an app in the console, and the app keys are written to .env.local or .env. The server mints a short-lived session token with createSessionToken from mroffice-embed/server, keeping the secret key server-side, and the page opens the editor with open() from mroffice-embed or the hosted embed.js script. The source lists co-editing, uploads, exports, printing and saves returned to your server in a signed callback. The free plan covers 1,000 sessions a month on localhost and 100 on your own domains, across up to 2 apps. Because this is a hosted commercial service, the announcement says your own app is not bound by the repository's AGPL licence.

For AI apps there is an MCP server. The hosted endpoint is https://mcp.mroffice.ai/mcp, signed in with an MR Office account and no key, or npx -y mroffice-mcp runs locally. The source is in apps/mcp. MR Office also describes itself as an OAuth 2.1 authorization server using PKCE, client ID metadata documents and dynamic registration, so an app can sign people in with an MR Office account.

Self-hosting means the AGPL route. The editors ship as React packages on npm (mroffice-docs, mroffice-core and one package per editor), and the playground runs at localhost:5178 after a build. If people use a modified version over a network, you must offer them its complete source and keep the MR Office attribution described in NOTICE.md. A commercial licence is available by email.

Limits and open questions

Prices above the free embed tier are not given in the source, and neither are the limits on the MCP endpoint or the OAuth server. The star and fork counts are a snapshot of one repository on one date. The biggest practical constraint is the AGPL network clause: a team that modifies the self-hosted editors and serves them to users takes on a source disclosure obligation, which is why the hosted embed exists as a separate, licensed path. Anyone who needs .docx round-tripping cannot get it from the open-source packages alone.

What this means for building apps with AI

The MCP server is the part most likely to matter to people assembling AI features into an app, since it lets a model open, read, edit and export documents inside a real editor rather than working on raw text. If you are wiring a model into an app you are building, the notes on adding AI to your app cover that layer. Draftship builds apps from a plain-language description, with a built-in database, user sign-in and hosting, and paid plans add a choice of model, source code access, custom domains and GitHub push. It is not affiliated with MR Office, and nothing here suggests the two work together.

Primary sources

This article was drafted with AI assistance from the primary sources listed below and checked automatically against them. An editor hasn't reviewed it yet.