Groupdocs Search MCP
Overview
Description from the maker (original English)
MCP server for GroupDocs.Search — index documents and run full-text search via AI agents.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi2 of 2 passedChecked from public information; code not scanned yet
- UsageiVery new★ 0
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: Search & AI memory
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 2 of 2 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_MCP_INDEX_PATH,GROUPDOCS_LICENSE_PATH,GROUPDOCS_METERED_PUBLIC_KEY,GROUPDOCS_METERED_PRIVATE_KEY
You need
- DockerDocker installed
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-search": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GROUPDOCS_MCP_STORAGE_PATH",
"-e",
"GROUPDOCS_MCP_OUTPUT_PATH",
"-e",
"GROUPDOCS_MCP_INDEX_PATH",
"-e",
"GROUPDOCS_LICENSE_PATH",
"-e",
"GROUPDOCS_METERED_PUBLIC_KEY",
"-e",
"GROUPDOCS_METERED_PRIVATE_KEY",
"ghcr.io/groupdocs-search/search-net-mcp:26.10.1"
],
"env": {
"GROUPDOCS_MCP_STORAGE_PATH": "your-value",
"GROUPDOCS_MCP_OUTPUT_PATH": "your-value",
"GROUPDOCS_MCP_INDEX_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-search --env GROUPDOCS_MCP_STORAGE_PATH=your-value --env GROUPDOCS_MCP_OUTPUT_PATH=your-value --env GROUPDOCS_MCP_INDEX_PATH=your-value --env GROUPDOCS_LICENSE_PATH=your-value --env GROUPDOCS_METERED_PUBLIC_KEY=your-value --env GROUPDOCS_METERED_PRIVATE_KEY=your-value -- docker run -i --rm -e GROUPDOCS_MCP_STORAGE_PATH -e GROUPDOCS_MCP_OUTPUT_PATH -e GROUPDOCS_MCP_INDEX_PATH -e GROUPDOCS_LICENSE_PATH -e GROUPDOCS_METERED_PUBLIC_KEY -e GROUPDOCS_METERED_PRIVATE_KEY ghcr.io/groupdocs-search/search-net-mcp:26.10.1Fill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"groupdocs-search": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GROUPDOCS_MCP_STORAGE_PATH",
"-e",
"GROUPDOCS_MCP_OUTPUT_PATH",
"-e",
"GROUPDOCS_MCP_INDEX_PATH",
"-e",
"GROUPDOCS_LICENSE_PATH",
"-e",
"GROUPDOCS_METERED_PUBLIC_KEY",
"-e",
"GROUPDOCS_METERED_PRIVATE_KEY",
"ghcr.io/groupdocs-search/search-net-mcp:26.10.1"
],
"env": {
"GROUPDOCS_MCP_STORAGE_PATH": "your-value",
"GROUPDOCS_MCP_OUTPUT_PATH": "your-value",
"GROUPDOCS_MCP_INDEX_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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"groupdocs-search": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GROUPDOCS_MCP_STORAGE_PATH",
"-e",
"GROUPDOCS_MCP_OUTPUT_PATH",
"-e",
"GROUPDOCS_MCP_INDEX_PATH",
"-e",
"GROUPDOCS_LICENSE_PATH",
"-e",
"GROUPDOCS_METERED_PUBLIC_KEY",
"-e",
"GROUPDOCS_METERED_PRIVATE_KEY",
"ghcr.io/groupdocs-search/search-net-mcp:26.10.1"
],
"env": {
"GROUPDOCS_MCP_STORAGE_PATH": "your-value",
"GROUPDOCS_MCP_OUTPUT_PATH": "your-value",
"GROUPDOCS_MCP_INDEX_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_PATHenvGROUPDOCS_MCP_OUTPUT_PATHenvGROUPDOCS_MCP_INDEX_PATHenvGROUPDOCS_LICENSE_PATHenvGROUPDOCS_METERED_PUBLIC_KEYenvGROUPDOCS_METERED_PRIVATE_KEYenv
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
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 11, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account groupdocs-search, which owns the repo
- ✓ Pass
Still maintained
Code last changed 27 days ago
- … 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 Search & AI memoryi
- More stars than 0% of the other 5863 servers in this category
- Published to the registry more recently than 59% of the other 5863 servers in this category
- Basic checks equal to or better than 100% of the other 5863 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 Search MCP safe?
It passed 2 of 2 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 27 days ago, and the latest version (26.10.1) reached the registry 26 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
What can I use instead?
In the same category: Ruflo, Context7, Metabase
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.Search MCP Server
MCP server that exposes GroupDocs.Search as AI-callable tools for Claude, Cursor, GitHub Copilot, and other MCP agents. It indexes folders of PDF, Office, email, archive and 70+ other document formats locally, then answers full-text, boolean, phrase, fuzzy and date-range queries over them — documents never leave your machine.
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/.
This product ships via Docker (GHCR) only. The GroupDocs.Search engine DLL is about 200 MiB and ships ONNX Runtime natives, so the packed tool (~281 MiB) exceeds NuGet.org's 250 MB limit — dnx and dotnet tool install are not available for it. When a slimmer engine packs under the limit, the standard NuGet flow returns (see the revert notes in .github/workflows/publish_prod.yml).
docker run --rm -i \
-v $(pwd)/documents:/data \ ghcr.io/groupdocs-search/search-net-mcp:latest
Images are multi-arch (linux/amd64 + linux/arm64), tagged latest plus an immutable version tag per release (e.g. :26.10.1). To pin, replace :latest with the version tag — recommended for shared configs and CI.
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 indexing fails with *"The index folder … is not writable"*. Add --user so the container writes as you:
docker run --rm -i --user "$(id -u):$(id -g)" \
-v $(pwd)/documents:/data \ ghcr.io/groupdocs-search/search-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", …]. Docker Desktop on Windows and macOS does not need this.
Where the index lives
Search is the one stateful server in the GroupDocs MCP family: an index is a persistent, searchable copy of your documents' text that survives restarts. By default it is kept in a .groupdocs-search-index folder inside the documents folder (/data/.groupdocs-search-index in the container), so the one volume mount above is all you need and the index is never indexed itself.
If the documents folder is read-only, keep the index in its own folder:
docker run --rm -i \
-v /path/to/documents:/data:ro \ -v /path/to/index:/index -e GROUPDOCS_MCP_INDEX_PATH=/index \ ghcr.io/groupdocs-search/search-net-mcp:latest
Available MCP Tools
| Tool | Description |
|---|---|
add_to_index | Indexes a file, a folder (recursively), or the whole storage folder. Creates the index on demand. |
search | Finds the documents that match a query, ranked by relevance, with occurrence counts — returned as JSON |
get_text_fragments | Returns the matching passages with surrounding words, so the agent can quote or answer from them |
update_index | Re-reads changed files, adds new files in indexed folders, drops deleted ones |
remove_from_index | Removes an indexed path (a folder or file passed to add_to_index) from the index; files on disk are untouched |
create_index | Creates or opens a named index (contracts, hr/2026), or recreates it empty |
get_index_info | Reports whether an index exists, its document count, indexed paths, version, and the other indexes — as JSON |
get_license_status | Reports the active licensing mode (evaluation / licensed / metered), the engine version, and — under metered — the consumed quantity and credit. Processes no document. |
Paths are always relative to the documents folder (contracts, reports/2026/q3.pdf), and indexes are referred to by name, never by filesystem path. Several named indexes can live side by side.
Query syntax (GroupDocs.Search DSL): single words (invoice); phrases in double quotes ("force majeure" — unquoted multi-word input does not match); AND, OR, NOT and parentheses; ? character wildcards (?ffect, princip?(2~4)); daterange(2026-01-01 ~~ 2026-06-30); number ranges (100 ~~ 500); field prefixes (filename: lease); regular expressions starting with ^; and fuzzy matching via the fuzzy argument.
Indexable formats include PDF, DOC/DOCX, XLS/XLSX, PPT/PPTX, ODT/ODS/ODP, RTF, TXT, HTML, EPUB, FB2, EML/EMLX/MSG, PST/OST, ONE and ZIP — including documents inside archives and email attachments. get_index_info with includeSupportedFormats: true lists the engine's full set.
Example prompts for AI agents
Copy any of these into Claude Desktop, Cursor, or GitHub Copilot Chat after the server is connected.
- Make a folder searchable: *"Index everything in my contracts folder."*
- Find the right documents: *"Which contracts mention a termination penalty?"*
- Read the evidence, not the file list: *"Show me the paragraphs that talk about \"force majeure\", with the file each one comes from."*
- Keep it current: *"I edited some files in reports — refresh the index and search for the Q3 forecast again."*
- Separate collections: *"Create an index called hr for the HR folder, then search it for parental leave."*
Licensing
The MCP server itself is MIT; the underlying GroupDocs.Search engine requires a license for production use. Without one the server runs in evaluation mode, and the limits are counts, not watermarks — results look complete and are not:
- An index holds at most 100 documents (across all indexes of a repository); indexing stops there.
- A search returns at most 10 documents.
- Every tool response carries an
evaluationnote while this applies. - Full list: evaluation limitations.
There are two ways to license the server.
License file — mount your GroupDocs.Search.lic (or GroupDocs.Total.lic) into the container and point GROUPDOCS_LICENSE_PATH at it. 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.
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:
- 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. - Reference them indirectly if your client supports it (Claude Code expands
${VAR}; VS Code uses${env:VAR}and${input:...}). - A literal value in a user-scoped config (for example
~/.claude.json) is acceptable for a single developer. - 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-search/search-net-mcp:latest
Configuration
| Variable | Description | Default |
|---|---|---|
GROUPDOCS_MCP_STORAGE_PATH | Folder with the documents to index; tool paths are relative to it | ./Files (/data in the image) |
GROUPDOCS_MCP_OUTPUT_PATH | *(Optional)* writable folder; indexes go under it when GROUPDOCS_MCP_INDEX_PATH is not set | GROUPDOCS_MCP_STORAGE_PATH |
GROUPDOCS_MCP_INDEX_PATH | *(Optional)* folder that holds the indexes, one sub-folder per index name | /.groupdocs-search-index |
GROUPDOCS_LICENSE_PATH | Path to a GroupDocs license file, as seen inside the container. Ignored when metered keys are set | (evaluation mode) |
GROUPDOCS_METERED_PUBLIC_KEY | Metered (pay-per-use) public key. Needs the private key too; takes precedence over GROUPDOCS_LICENSE_PATH | (unset) |
| GROUPDOCS_METERED_PRIVATE_KEY | Metered priv