Growi MCP Server

What growilabs/growi-mcp-server MCP server does

The growilabs/growi-mcp-server MCP server connects MCP-compatible agents to GROWI wiki instances. It provides tools for finding pages, reading full Markdown content or selected sections, inspecting page outlines, and retrieving page metadata. Agents can also create, replace, partially edit, duplicate, rename, and delete pages. Bulk deletion is supported.

The server covers related wiki operations beyond page bodies. It can read and update tags, search the tag catalog, add or remove comments, inspect revision history, and create, list, or delete share links. It also exposes page listings, recently updated pages, and user-specific recent pages. The older getPage operation remains available as an alias, but is deprecated in favor of the more targeted page-reading tools.

How it works

The package runs as a local stdio MCP server using npm and communicates with GROWI through its APIs. A configuration can define one GROWI application or several. Each application uses a numbered name, base URL, and API token; an optional default app name selects which configured instance should be used when multiple apps are present.

The growilabs/growi-mcp-server MCP server also includes optional Vault commands for synchronizing a local, read-only git clone of a GROWI Vault, locating that clone, and decoding Vault filenames. These commands use the same application configuration and require Git 2.31 or newer. They are separate from the MCP tool interface but can support local wiki searching workflows.

Setup and configuration

Install and run the server with:

npx -y @growi/mcp-server

Register that command in the MCP client configuration and provide at least these variables for the first application:

• GROWI_APP_NAME_1: the local name assigned to the GROWI application
• GROWI_BASE_URL_1: the GROWI instance URL
• GROWI_API_TOKEN_1: an API token for authentication

Additional numbered sets can connect to other GROWI applications. The repository documents direct setup as an alternative to installing its setup skill. It also provides skills for guided setup and for saving content with suggested GROWI paths.

Tools and capabilities

The growilabs/growi-mcp-server MCP server includes capabilities for:

• Searching pages and tags
• Reading complete pages, selected sections, outlines, and page metadata
• Creating, updating, partially editing, duplicating, renaming, and deleting pages
• Listing root pages, child pages, recent pages, and page-listing summaries
• Managing page tags and comments
• Reviewing revisions and obtaining revision diffs
• Creating, listing, and deleting page share links
• Publishing or unpublishing pages, where supported by the available package version

Section reads can use heading text or line ranges. Partial edits support replacement operations and a dry-run diff preview. Revision-change and batch-diff tools require GROWI 7.5.6 or later.

Limitations and notes

GROWI 7.3.x or later is the recommended server version, while some functionality is available from GROWI 7.2.5 onward. The revision-change and revision-diff operations specifically require GROWI 7.5.6 or newer. Revision listings omit revision bodies and return body lengths instead. The getPage tool is deprecated and is scheduled for removal in version 2.0.0; new integrations should use the outline, section, or whole-content operations.

The server requires a configured GROWI endpoint and credential. Multiple application connections use numbered environment-variable groups, so each target must be configured separately. Vault synchronization additionally requires a suitable Git installation.