A
licenseA
qualityA
maintenanceAn MCP server for MediaWiki instances with multi-wiki support, providing full read/write access via REST and Action APIs across multiple named wikis.
21
22 npm
3
MIT
mcp-mediawiki-crunchtools
by crunchtools
Related Servers
Alternatives to mcp-mediawiki-crunchtools
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for MediaWiki wikis. Search, read, edit, and manage wiki content from AI assistants. Includes formatting, link checking, revision history, and markdown conversion.4323MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables full management of WikiJS instances, supporting operations like page creation, searching, and updating. It also provides tools for knowledge graph exploration, content summarization, and retrieval of wiki statistics.12 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables LLM clients to read, search, create, edit, and manage pages, files, and metadata on any MediaWiki wiki through MCP tools, including extension packs for Semantic MediaWiki, Cargo, Wikibase, Bucket, and NeoWiki. Supports multiple wikis with OAuth authentication and configurable access controls.8 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables LLM clients to read, search, create, update, delete, move, protect, and upload content on any MediaWiki wiki through MCP tools and resources. It also supports wiki management, OAuth, and extension-specific queries for NeoWiki, Semantic MediaWiki, Bucket, Cargo, and Wikibase.8 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server that enables AI agents to interact with Wiki.js as a knowledge base through a comprehensive set of 29 tools for content retrieval and management. It supports full-text search, page versioning, and asset browsing with optional write operations secured by safety gates.2917 npm8MIT
TDQS
B3.2/5.0
Scored across 19 tools
Disambiguation4/5
Most tools target clearly distinct resources and actions: page CRUD, search, categories, files, users, and site metadata are well separated. There is minor overlap among get_page_tool, get_page_html_tool, and parse_wikitext_tool, since all relate to page content/rendering, but their inputs and outputs are described distinctly enough to choose correctly.
Naming Consistency5/5
All 19 tool names follow the same snake_case pattern with a consistent _tool suffix, and nearly all use a predictable verb_noun structure (get_page_tool, list_pages_tool, create_page_tool). The only slight deviation is search_tool, which omits an explicit noun, but it remains readable and consistent with the overall convention.
Tool Count3/5
The 19-tool surface is broad but somewhat heavy for a MediaWiki integration; it covers many useful areas, yet some tools could be consolidated or split into optional groups. Per the rubric, 16–25 tools is borderline, so this earns a middle score rather than a high one.
Completeness4/5
The set covers core wiki workflows well: search, page read/create/edit/delete/move, categories, recent changes, parsing, namespaces, users, and files. Gaps remain around revision history and diffs, file uploads, and richer user/auth management, but these are minor enough that agents can often work around them.
Maintenance
ActivityActive
ResponsivenessNo issues