Growi MCP Server vs MCP Bling — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Growi MCP Server vs MCP Bling
In-depth architectural comparison of the Growi MCP Server and MCP Bling 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
Growi MCP Server
Other Tools and Integrations · Local stdio
Quality: 74/100 (Great) | Auth: API Key required
MCP Bling
Other Tools and Integrations · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Growi MCP Server if you need specialized Other Tools and Integrations tools running via a local process. Choose MCP Bling 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 Growi MCP Server 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: GROWI_APP_NAME_1, GROWI_BASE_URL_1, GROWI_API_TOKEN_1.
Give AI agents a persistent identity and cross-platform visual style. Includes WOW (Weird Office Workers) random-identity generator with rarity tiers and screenshot-ready share cards. npx -y bling-bag
Category & Scope
Tools & Capabilities Breakdown
Growi MCP Server Tools (32)
searchPages
Search pages by keywords
createPage
Create a new page
updatePage
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)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Growi MCP Server is categorized under Other Tools and Integrations and uses a local stdio subprocess. In contrast, MCP Bling belongs to Other Tools and Integrations using local stdio subprocess. Select Growi MCP Server when you need capabilities focused on other tools and integrations and MCP Bling when you require tools for other tools and integrations.
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
getPageInfo
Get detailed page information
+20 more tools listed on main page
MCP Bling Tools (5)
get_identity
Who's your bot? Pull up the full identity — name, personality, quirks, appearance, and theme colours. Returns whatever's configured in bling.json. Errors if bling.json is missing or invalid.
get_theme_for_platform
Get your bot's colours formatted for a specific platform. Supported: terminal (ANSI codes), web (CSS variables), slack, discord, ide. Unknown platforms get the raw hex colours.
roll_identity
Give your bot a random identity. Pick a variant: wow (Weird Office Workers — quirky office drones, default) or legends (historical figures in absurd corporate roles). Returns a name, job title, traits, rarity score, and a screenshot-ready share card. Stores the roll for save_last_roll.
save_last_roll
Save the most-recent roll as your bot's permanent identity. Errors if no roll has happened this session — call roll_identity first. Writes to bling.json, backing up any existing config to bling.json.bak first. Returns the backup path (or null if nothing was overwritten).
get_rarity_report
Get the formatted share card for the most-recent roll — a plain-text block ready to screenshot and post. Errors if no roll has happened this session.