DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to connect Claude Code or Cursor to GenOffice over MCP with Genoffice

Start the Genoffice MCP server so an MCP client can create and edit Office files with no window open.

Who it is forA developer who wants an MCP-enabled coding agent to build Office documents as part of a larger automated workflow.

The problemInstalling a skill is not always possible in a shared or locked-down setup, and some teams prefer a standard protocol.

The outcomeThe MCP client lists the GenOffice tools and can create, convert and edit real Office files on your machine.

What you need first

  • A computer running macOS, Windows or Linux, with the GenOffice app downloaded from the releases page
  • Either a Genspark sign-in or an API key from a supported provider such as Claude, OpenAI or Gemini, or a local OpenAI-compatible server
  • For the agent use cases: Claude Code, Codex, Cursor, Gemini CLI or another supported coding agent installed on the same computer

Steps

  1. Install the GenOffice app and open Settings → Integrations.
  2. For Claude Code, copy the claude mcp add line shown there and run it in your terminal.
  3. For Cursor or Claude Desktop, copy the JSON block into the MCP settings of that client.
  4. Start the server with genoffice mcp if your client needs it started by hand.
  5. Ask the client to list the available tools, then run one small task such as creating a short .docx.

Prompt for your agent

Connect Claude Code to the GenOffice MCP server using the `claude mcp add` line from Settings → Integrations, then create a one-page .docx named <file name> in <folder>. Expected output: the .docx file and a list of the tools used. Verify that the file opens in Word.

Caveat. The HTTP server for the visible Word editor is a separate option in Settings → Integrations, so turn it on only if you need that visible editor tab.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page