Growi MCP Server
by
Connects AI models to GROWI wiki content, enabling search and retrieval of organizational knowledge for context‑aware responses.
Growi MCP Server Overview
What is Growi MCP Server about?
Provides a Model Context Protocol (MCP) server that bridges large language models with a GROWI wiki instance. By exposing page, tag, comment, revision, and share‑link operations through a standardized API, LLMs can fetch up‑to‑date organizational knowledge and generate accurate, context‑aware answers.
How to use Growi MCP Server?
- Install – run the server with npm:
npx @growi/mcp-server - Configure environment variables:
GROWI_BASE_URL– the base URL of your GROWI instance.GROWI_API_TOKEN– an API token with sufficient permissions.
- Add to your MCP client configuration (e.g.,
mcp-config.json):{ "mcpServers": { "growi": { "command": "npx", "args": ["@growi/mcp-server"], "env": { "GROWI_BASE_URL": "https://your-growi-instance.com", "GROWI_API_TOKEN": "your_growi_api_token" } } } } - Start the server (
pnpm dev:clifor testing,pnpm startfor production) and invoke the exposed tools from your LLM integration.
Key features of Growi MCP Server
- Page Management: search, create, update, delete, duplicate, rename, publish/unpublish, retrieve details, recent pages, and hierarchical listings.
- Tag Management: get, update, list, and search page tags.
- Comments: retrieve comments attached to pages.
- Revision History: list revisions and fetch specific revision data.
- Share Links: create, list, and delete shareable links for pages.
- User‑specific data: fetch recent pages per user.
- Full TypeScript support via the GROWI SDK.
Use cases of Growi MCP Server
- Knowledge‑augmented chatbots that answer employee queries using the latest wiki content.
- Automated documentation assistants that suggest relevant pages while drafting new content.
- Contextual code assistants that pull internal design docs or API specs from GROWI.
- Compliance auditors that retrieve revision histories and comment threads for regulatory reviews.
- Personalized knowledge feeds delivering recent pages tailored to individual users.
FAQ from the Growi MCP Server
Q: Which GROWI versions are supported?
- Recommended: GROWI v7.3.x or newer. Some functionality works on v7.2.x and earlier.
Q: Do I need to build the project before running it?
- For development you can run directly with
npx @growi/mcp-server. For production, build withpnpm buildand run the compileddist/index.js.
Q: How do I secure the connection to GROWI?
- Use a strong API token (
GROWI_API_TOKEN) and ensure the server runs behind appropriate network controls (HTTPS, firewalls).
Q: Can I customize which tools are exposed?
- The server follows the MCP specification; you can enable/disable tools by editing the source or contributing to the repository.
Q: What if the server cannot connect to GROWI?
- Verify network connectivity (
curl -v $GROWI_BASE_URL/_api/v3/healthcheck) and Docker network settings if using the devcontainer.
Growi MCP Server's README
@growi/mcp-server
A Model Context Protocol (MCP) server that connects AI models to GROWI wiki content. Enables LLMs to search and retrieve information from your organization's knowledge base for accurate, context-aware responses.
Key Features
- 🔍 GROWI page search and retrieval
- 📝 Page management
- 🏷️ Tag management
- 📋 Comment management
- 🔗 Share link management
Supported GROWI Versions
- GROWI v7.3.x or higher recommended
- *GROWI v7.3.x is scheduled for release in 2025Q2
- Some features are available on GROWI v7.2.x and below
- GROWI API
MCP Server Configuration
{
"mcpServers": {
"growi": {
"command": "npx",
"args": ["@growi/mcp-server"],
"env": {
"GROWI_BASE_URL": "https://your-growi-instance.com",
"GROWI_API_TOKEN": "your_growi_api_token"
}
}
}
}
Available Tools (Features)
Page Management
searchPages- Search pages by keywordscreatePage- Create a new pageupdatePage- Update an existing pagedeletePages- Delete pages (bulk operation supported)duplicatePage- Duplicate a page (including child pages)renamePage- Change page name and pathgetPage- Get a page datagetPageInfo- Get detailed page informationgetRecentPages- Get list of recently updated pagesgetPageListingRoot- Get root page listgetPageListingChildren- Get child pages of specified pagepageListingInfo- Get summary information of page listingspublishPage/unpublishPage- Set page publish/unpublish status
Tag Management
getPageTag- Get tags of a pageupdateTag- Update tags of a pagegetTagList- Get list of tagssearchTags- Search tags
Comments & Discussions
getComments- Get comments of a page
Revision Management
listRevisions- Get page edit historygetRevision- Get details of a specific revision
Share Links
createShareLink- Create a share linkgetShareLinks- Get share links of a pagedeleteShareLinks- Delete share linksdeleteShareLinkById- Delete a specific share link
User Information
getUserRecentPages- Get recent pages of a specific user
Configuration Options
Environment Variables
| Variable Name | Required | Description | Default Value |
|---|---|---|---|
GROWI_BASE_URL |
✅ | Base URL of GROWI instance | - |
GROWI_API_TOKEN |
✅ | GROWI API access token | - |
Developer Information
Requirements
- Node.js 18 or higher
- pnpm (recommended)
- GROWI instance (for development and testing)
Getting Started
- Clone the repository
git clone https://github.com/growilabs/growi-mcp-server.git
cd growi-mcp-server
- Install dependencies
pnpm install
- Set up environment variables
cp .env.example .env.local
# Edit .env.local to enter GROWI connection information
- Start the development server
# Test with MCP CLI
pnpm dev:cli
# Develop with MCP Inspector
pnpm dev:inspect
Build and Test
# Build
pnpm build
# Lint
pnpm lint
# Run in production
pnpm start
MCP Server Configuration
- Build
pnpm build
- MCP Server Configuration
{
"mcpServers": {
"growi": {
"command": "node",
"args": ["/Users/username/projects/growi-mcp-server/dist/index.js"],
"env": {
"GROWI_BASE_URL": "https://your-growi-instance.com",
"GROWI_API_TOKEN": "your_growi_api_token"
}
}
}
}
[!NOTE] Set the absolute path to the built output in "args"
Troubleshooting
When unable to connect to GROWI
- Check connectivity
curl -v http://app:3000/_api/v3/healthcheck - If the
apphostname cannot be resolved, check the devcontainer network and verify it includesgrowi_devcontainer_default- The
.devcontainer/devcontainer.jsonfile sets--networkinrunArgs, so rebuilding the container should apply this setting - To add manually, run the following:
- Run
docker networkcommand on the docker host machine
docker network connect growi_devcontainer_default growi-mcp-server-dev - Run
- The
Contributing
Contributions to the project are welcome!
How to Contribute
- Issue Reports: Bug reports and feature requests via GitHub Issues
- Pull Requests:
- Fork and create a branch
- Implement changes
- Add tests (if applicable)
- Create a pull request
Development Guidelines
- Coding Standards: Use Biome
- Commit Messages: Follow Conventional Commits
License
This project is released under the MIT License.
Related Links
- GROWI Official Site - Open source wiki platform
- Model Context Protocol - Standard protocol for AI and tool integration
- GROWI SDK TypeScript - GROWI API TypeScript SDK
- FastMCP - MCP server development framework
Notice
This MCP server is under development. APIs may change without notice. Please test thoroughly before using in production environments.
Growi MCP Server Reviews
Login Required
Please log in to share your review and rating for this MCP.
Actions
Growi MCP Server's Information
- Author
- growilabs
- Category
- Knowledge & Memory
- Language
- TypeScript
- License
- MIT License
- Version
- v1.1.0
- Stars
- 6
- Updated
- about 1 month ago
Configuration
{
"mcpServers": {
"growi": {
"command": "npx",
"args": [
"@growi/mcp-server"
],
"env": {
"GROWI_BASE_URL": "<YOUR_GROWI_BASE_URL>",
"GROWI_API_TOKEN": "<YOUR_GROWI_API_TOKEN>"
}
}
}
}Configure Clients
Related MCP Servers
Discover more MCP servers with similar functionality and use cases
Cognee
by topoteretes
Enables AI agents to store, retrieve, and reason over past conversations, documents, images, and audio transcriptions by loading data into graph and vector databases with minimal code.
Basic Memory
by basicmachines-co
Basic Memory is a local-first knowledge management system that allows users to build a persistent semantic graph from conversations with AI assistants. It addresses the ephemeral nature of most LLM interactions by providing a structured, bi-directional knowledge base that both humans and LLMs can read and write to.
Obsidian Markdown Notes
by smithery-ai
mcp-obsidian is a connector that allows Claude Desktop to read and search an Obsidian vault or any directory containing Markdown notes.
Mcp Server Qdrant
by qdrant
Provides a semantic memory layer on top of the Qdrant vector search engine, enabling storage and retrieval of information via the Model Context Protocol.
Context Portal
by GreatScottyMac
A database‑backed MCP server that stores project decisions, progress, architecture, custom data, and vector embeddings, allowing AI assistants in IDEs to retrieve precise, up‑to‑date context for generation tasks.
Obsidian MCP Server
by StevenStavrakis
Enables AI assistants to read, create, edit, move, delete, and organize notes and tags within an Obsidian vault.
Mem0 Mcp
by mem0ai
Provides tools to store, retrieve, and semantically search coding preferences via an SSE endpoint for integration with MCP clients.
Graphlit MCP Server
by graphlit
Enables integration between MCP clients and the Graphlit platform, providing ingestion, retrieval, RAG, and publishing capabilities across a wide range of data sources and tools.
Chroma MCP Server
by chroma-core
Provides vector, full‑text, and metadata‑based retrieval powered by Chroma for LLM applications, supporting in‑memory, persistent, HTTP, and cloud clients as well as multiple embedding functions.