Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Groupdocs Parser MCP

by groupdocs-parserversion 26.11.0i★ –iRuns on your computer
Registry nameio.github.groupdocs-parser/groupdocs-parser-mcp

Install

Overview

Description from the maker (original English)

MCP server for GroupDocs.Parser — extract text, images, metadata, tables, barcodes via AI.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: GROUPDOCS_MCP_STORAGE_PATH, GROUPDOCS_MCP_OUTPUT_PATH, GROUPDOCS_LICENSE_PATH, GROUPDOCS_METERED_PUBLIC_KEY, GROUPDOCS_METERED_PRIVATE_KEY

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "groupdocs-parser": {
      "command": "dnx",
      "args": [
        "GroupDocs.Parser.Mcp",
        "--yes"
      ],
      "env": {
        "GROUPDOCS_MCP_STORAGE_PATH": "your-value",
        "GROUPDOCS_MCP_OUTPUT_PATH": "your-value",
        "GROUPDOCS_LICENSE_PATH": "your-value",
        "GROUPDOCS_METERED_PUBLIC_KEY": "your-value",
        "GROUPDOCS_METERED_PRIVATE_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add groupdocs-parser --env GROUPDOCS_MCP_STORAGE_PATH=your-value --env GROUPDOCS_MCP_OUTPUT_PATH=your-value --env GROUPDOCS_LICENSE_PATH=your-value --env GROUPDOCS_METERED_PUBLIC_KEY=your-value --env GROUPDOCS_METERED_PRIVATE_KEY=your-value -- dnx GroupDocs.Parser.Mcp --yes

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "groupdocs-parser": {
      "command": "dnx",
      "args": [
        "GroupDocs.Parser.Mcp",
        "--yes"
      ],
      "env": {
        "GROUPDOCS_MCP_STORAGE_PATH": "your-value",
        "GROUPDOCS_MCP_OUTPUT_PATH": "your-value",
        "GROUPDOCS_LICENSE_PATH": "your-value",
        "GROUPDOCS_METERED_PUBLIC_KEY": "your-value",
        "GROUPDOCS_METERED_PRIVATE_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "groupdocs-parser": {
      "type": "stdio",
      "command": "dnx",
      "args": [
        "GroupDocs.Parser.Mcp",
        "--yes"
      ],
      "env": {
        "GROUPDOCS_MCP_STORAGE_PATH": "your-value",
        "GROUPDOCS_MCP_OUTPUT_PATH": "your-value",
        "GROUPDOCS_LICENSE_PATH": "your-value",
        "GROUPDOCS_METERED_PUBLIC_KEY": "your-value",
        "GROUPDOCS_METERED_PRIVATE_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • GROUPDOCS_MCP_STORAGE_PATH env
  • GROUPDOCS_MCP_OUTPUT_PATH env
  • GROUPDOCS_LICENSE_PATH env
  • GROUPDOCS_METERED_PUBLIC_KEY env
  • GROUPDOCS_METERED_PRIVATE_KEY env

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account groupdocs-parser, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32380 servers in this category
  • Published to the registry more recently than 99% of the other 32380 servers in this category
  • Basic checks equal to or better than 100% of the other 32380 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Groupdocs Parser MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (26.11.0) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need .NET on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Dechonet MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Dechonet MCP

by node-man

30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.

Computer or cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

GroupDocs.Parser MCP Server

MCP server that exposes GroupDocs.Parser as AI-callable tools for Claude, Cursor, GitHub Copilot, and other MCP agents.

Installation

One-click installs pre-fill every supported setting: edit the placeholder host path in

the volume mount after install; an empty GROUPDOCS_LICENSE_PATH runs in evaluation mode.

More clients - ready-made configs for Claude Code, Codex CLI, Visual Studio 2022,

Cursor, Windsurf, Cline, and JetBrains Rider live in install/generated/.

Requires .NET 10 SDK.

Run directly with `dnx` (recommended — no install step):

dnx GroupDocs.Parser.Mcp --yes

Pulls the latest stable release on every invocation. To pin to a specific version (recommended for shared configs and CI), append @ :

dnx GroupDocs.Parser.Mcp@26.11.0 --yes

Or install as a global dotnet tool:

dotnet tool install -g GroupDocs.Parser.Mcp

groupdocs-parser-mcp

The first launch downloads ~230 MB, once. The engine carries its table and barcode models,

so the tool ships as one package per platform (win-x64, win-arm64, linux-x64,

linux-arm64, osx-x64, osx-arm64) and dnx picks the one for your machine. Later launches

use the NuGet cache. If your MCP client times out on that first start, run the dnx command

once in a terminal, then restart the client.

Or run via Docker:

docker run --rm -i \

-v $(pwd)/documents:/data \ ghcr.io/groupdocs-parser/parser-net-mcp:latest

Images are multi-arch (linux/amd64 + linux/arm64), tagged latest plus an immutable version tag per release (e.g. :26.11.0). To pin, replace :latest with the version tag - recommended for shared configs and CI. Versions 26.10.2 and earlier were published only as Docker images.

Linux: run the container as your user

The image runs as a non-root user (uid 1654). On Linux a mounted folder keeps its host owner, so a folder you own is read-only inside the container and extract_images cannot save its files — the error ends with *"Fix: the server cannot write to the output folder"*. Add --user so the container writes as you:

docker run --rm -i --user "$(id -u):$(id -g)" \

-v $(pwd)/documents:/data \ ghcr.io/groupdocs-parser/parser-net-mcp:latest

MCP client configs (JSON) do not run a shell, so put the numbers in directly — id -u and id -g print them, typically 1000: "args": ["run", "--rm", "-i", "--user", "1000:1000", "-v", …]. Read-only tools (extract_text, extract_tables, extract_metadata, extract_barcodes, get_document_info) work without it. Docker Desktop on Windows and macOS does not need this.

Native prerequisites

When you run the server natively (via dnx or the global dotnet tool) on Linux, the engine's image-extraction and barcode paths need two native libraries:

PlatformSetup
WindowsNothing — GDI+ is built into the OS.
Linuxsudo apt-get install -y libgdiplus libfontconfig1
macOSbrew install mono-libgdiplus if a tool reports DllNotFoundException: libgdiplus
DockerNothing — the image already bundles them.

Available MCP Tools

ToolDescription
extract_textExtracts plain text from a document (whole document or a single page). Truncates very large outputs.
extract_imagesExtracts all embedded images and saves them to storage as _image . files
extract_metadataExtracts metadata (author, title, dates, custom properties, EXIF, XMP, IPTC) and returns it as JSON
extract_tablesExtracts tables from a document as Markdown (default — renders in chat) or structured JSON
extract_barcodesDetects all barcodes / QR codes and returns their decoded values, types, and positions as JSON
get_document_infoReturns the file type, page count, and size of a document as JSON (without modifying it)
get_license_statusReports the active licensing mode (evaluation / licensed / metered), the engine version, and — under metered — the consumed quantity and credit. Processes no document.

All tools support PDF, DOCX, XLSX, PPTX, HTML, EPUB, MSG, EML, JPG, PNG, TIFF, and 50+ more document and image formats.

Example prompts for AI agents

Copy any of these into Claude Desktop, Cursor, or GitHub Copilot Chat after the server is connected.

  1. Get a document's structure: *"How many pages does invoice.pdf have, and what format is it?"*
  2. Pull a text snippet: *"Extract the text from page 2 of contract.docx."*
  3. Mine the metadata: *"What's the author and creation date of report.xlsx?"*
  4. Read a structured table: *"Pull the line items table out of invoice.pdf as Markdown."*
  5. Scan for barcodes: *"Are there any QR codes in shipping-label.png? If so, what do they decode to?"*

Licensing

The MCP server itself is MIT; the underlying GroupDocs.Parser engine requires a license for production use. Without one the server runs in evaluation mode, and the limits bite hard for extraction — the output looks valid and is silently incomplete:

  • Text extraction: only the first 1,600 characters and 20 lines per file, and only the first 5 pages, sheets or slides. Formatted-text and structure extraction add a 20-row cap for spreadsheets.
  • Metadata extraction: only 5 properties per file.
  • Only 100 files per session, and outputs carry evaluation marks.
  • Full list: evaluation limitations.

There are two ways to license the server.

License file — point GROUPDOCS_LICENSE_PATH at your GroupDocs.Parser.lic (or GroupDocs.Total.lic). With Docker, mount the file into the container and use the path as seen inside it (see Usage with Claude Desktop). Works offline.

Metered (pay-per-use) — set both GROUPDOCS_METERED_PUBLIC_KEY and GROUPDOCS_METERED_PRIVATE_KEY. You are billed for what you actually process, which suits AI agents well because their usage is bursty and hard to predict up front. If both a metered key pair and a license file are configured, metered wins and the file is ignored.

Metered mode needs outbound connectivity. Usage is reported to GroupDocs servers, so

air-gapped or firewalled deployments must allow that egress — or use a license file instead.

Call the `get_license_status` tool at any time to see which mode is active, and — under metered — the consumed quantity and remaining credit. It processes no document and changes nothing, so it is the cheapest way to confirm a setup before a real run.

Keeping the private key out of your config

The metered private key is a secret. MCP client configs are plain files on disk, and a project-scoped .mcp.json is committed by convention, so prefer, in order:

  1. Set the variables in your OS environment and leave them out of the config entirely. An stdio MCP server inherits its client's environment, so this works in every client. On macOS note that an app launched from Finder does not inherit shell exports — use launchctl setenv, or launch the client from a terminal.
  2. Reference them indirectly if your client supports it (Claude Code expands ${VAR}; VS Code uses ${env:VAR} and ${input:...}).
  3. A literal value in a user-scoped config (for example ~/.claude.json) is acceptable for a single developer.
  4. Never commit a literal key in a project-scoped .mcp.json.

For Docker, forward the values without writing them into any file — the names alone, so the keys never appear in the command line:

docker run --rm -i \

-e GROUPDOCS_METERED_PUBLIC_KEY -e GROUPDOCS_METERED_PRIVATE_KEY \ -v /path/to/documents:/data \ ghcr.io/groupdocs-parser/parser-net-mcp:latest

Configuration

VariableDescriptionDefault
GROUPDOCS_MCP_STORAGE_PATHBase folder for input and output filescurrent directory
GROUPDOCS_MCP_OUTPUT_PATH*(Optional)* separate folder for output files (used by extract_images)GROUPDOCS_MCP_STORAGE_PATH
GROUPDOCS_LICENSE_PATHPath to a GroupDocs license file (under Docker, as seen inside the container). Ignored when metered keys are set(evaluation mode)
GROUPDOCS_METERED_PUBLIC_KEYMetered (pay-per-use) public key. Needs the private key too; takes precedence over GROUPDOCS_LICENSE_PATH(unset)
GROUPDOCS_METERED_PRIVATE_KEYMetered private key. Secret — pass it from the environment, never from a committed config(unset)

Usage with Claude Desktop

{

"mcpServers": { "groupdocs-parser": { "type": "stdio", "command": "dnx", "args": ["GroupDocs.Parser.Mcp", "--yes"], "env": { "GROUPDOCS_MCP_STORAGE_PATH": "/path/to/documents" } } } }

To pin to a specific version, replace "GroupDocs.Parser.Mcp" with

Only the beginning is shown; read the rest in the repo

Ask PopNx