Install guide

What you need

• Claude Code (included in the Claude Pro and Max plans): the desktop app's Code tab or the claude command line. No API key needed.
• Node.js 20 or later (nodejs.org). Check with node --version.
• A document editor based on OnlyOffice, opened in your browser: kDrive (Infomaniak), Nextcloud, ONLYOFFICE DocSpace…

1. Add the plugin to Claude Code

In a terminal:

claude plugin marketplace add maximlefebvre/onlyoffice-claude-bridge claude plugin install onlyoffice-bridge@onlyoffice-bridge

Or inside a claude session, type /plugin, add the marketplace maximlefebvre/onlyoffice-claude-bridge and install onlyoffice-bridge.

New sessions now start the bridge server automatically. Updates come through /plugin like any other plugin.

Using the Chat tab of Claude Desktop, or another MCP client? See other clients. Only one Claude session at a time can run the bridge: a second one reports that the port is in use.

2. Install the plugin in OnlyOffice

1. Open any document in your OnlyOffice editor, go to the Plugins tab and click Plugin Manager.

2. Click </> at the top right of the Plugin Manager (developer mode), paste this store address and confirm:

   https://maximlefebvre.github.io/onlyoffice-claude-bridge/store/index.html

3. Find Claude Bridge in the list and click Install.

4. Open it from the Plugins tab: a Claude Bridge panel appears on the left. It is installed for this browser and works in text documents, spreadsheets and presentations.

3. Check your browser

With a Claude session running, open the connection test and click Test connection. Then check the notes for your browser below.

Browser notes

Firefox	Since version 151, Firefox blocks the editor's plugin frame from reaching 127.0.0.1, without asking. The panel then shows Click Connect: click it, and a small relay window opens and carries the connection. The first time, Firefox asks in that window whether the site may access apps on this device: tick Remember and Allow. Keep the relay window open while you work (one per document tab); it closes by itself with the document. If nothing opens, allow pop-ups for the editor's site.
Chrome, Edge	Recent versions have a similar protection and should use the same relay window. Not tested yet inside an editor: if the panel cannot connect, please open an issue.
Safari	Not tested yet.

4. Approve the first connection

In the Claude Bridge panel, the status reads Approve the connection on your computer… and a dialog opens on your computer asking whether this browser may connect. Choose Allow.

The browser receives its own key and reconnects silently from then on. If no dialog can be shown (for example on a Linux server without a desktop), Claude asks you in the conversation instead.

On Linux the dialog uses zenity or kdialog. To revoke a browser later, ask Claude to list or revoke the paired browsers.

5. Try it

The panel shows a green dot and Connected to Claude. In Claude, ask for example:

• “Proofread my document and fix the typos, with track changes on.”
• “Make the header row bold, add borders and a column chart of the sales.”
• “Add a slide summarising the three key points, in Inter, on a dark background.”

Edits appear live in the document and can be undone with Ctrl/⌘+Z.

Troubleshooting

Panel shows “Click Connect”	Your browser blocks direct connections from the editor: click Connect to open the relay window, and keep it open.
Panel stays on “Connecting…” or “Reconnecting…”	Start (or restart) a Claude session, then run the test on the connection page.
“Connection denied”	The connection was refused in the dialog. Close and reopen the panel to ask again.
Claude says no document is connected	Open the Claude Bridge panel in that document. Each open document needs its panel open.
“Port in use”	Another Claude session already runs the bridge: close it, or use that session.
Old plugin version	In the Plugin Manager, remove Claude Bridge and install it again from the store.