Wenyan MCP vs Growi MCP Server — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Wenyan MCP vs Growi MCP Server
In-depth architectural comparison of the Wenyan MCP and Growi MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Wenyan MCP
Other Tools and Integrations · Local stdio
Quality: 47/100 (Fair) | Auth: API Key required
Growi MCP Server
Other Tools and Integrations · Local stdio
Quality: 80/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose Wenyan MCP if you need specialized Other Tools and Integrations tools running via a local process. Choose Growi MCP Server if your workspace requires Other Tools and Integrations integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Wenyan MCP when:
You need dedicated capabilities in the Other Tools and Integrations domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: WECHAT_APP_ID, WECHAT_APP_SECRET.
Primary tools included: One-click Markdown to WeChat draft publishing, Automatic upload of article images and cover photos, Support for multiple built-in and user-defined themes.
You need dedicated capabilities in the Other Tools and Integrations domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: GROWI_APP_NAME_1, GROWI_BASE_URL_1, GROWI_API_TOKEN_1, GROWI_APP_NAME_2, GROWI_BASE_URL_2, GROWI_API_TOKEN_2, GROWI_DEFAULT_APP_NAME.
Wenyan MCP is categorized under Other Tools and Integrations and uses a local stdio subprocess. In contrast, Growi MCP Server belongs to Other Tools and Integrations using local stdio subprocess. Select Wenyan MCP when you need capabilities focused on other tools and integrations and Growi MCP Server when you require tools for other tools and integrations.
Update an existing page (full-body replace; returns the new revision ID)
editPage
Edit parts of a page with string replacements without sending the whole body (supports dry-run diff preview)
deletePages
Delete pages (bulk operation supported)
duplicatePage
Duplicate a page (including child pages)
renamePage
Change page name and path
getPageOutline
Get the heading outline of a page (heading tree with line ranges and sizes, without the body); also detects setext-style (underline) headings
getPageSection
Read only a part of a page, addressed by heading text or line range
getPageWholeContents
Get the full markdown body of a page
getPage
**Deprecated, will be removed in 2.0.0.** Alias of `getPageWholeContents` kept for backward compatibility; use `getPageOutline`, `getPageSection`, or `getPageWholeContents` instead