A
licenseA
qualityA
maintenanceMCP server for MediaWiki wikis. Search, read, edit, and manage wiki content from AI assistants. Includes formatting, link checking, revision history, and markdown conversion.
43
20
MIT
mediawiki-mcp-server
Related Servers
Alternatives to mediawiki-mcp-server
Related Servers
- AlicenseNot gradedqualityCmaintenanceModel Context Protocol (MCP) Server for the mcp API.681MIT
- AlicenseNot gradedqualityFmaintenanceModel Context Protocol (MCP) server for Wiki.js with hierarchical documentation & Docker setup45MIT
OSRS MCP Serverofficial
AlicenseBqualityNot gradedmaintenanceMCP Server for interacting with Old School RuneScape Wiki API and game data files, providing tools to search the OSRS Wiki and access game data definitions through the Model Context Protocol.19411-- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol (MCP) server for converting files between different formats5MIT
- AlicenseNot gradedqualityBmaintenanceA generic, modular server for implementing the Model Context Protocol (MCP).5045ISC
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) server implementation for Autodesk Maya99MIT
TDQS
A4.2/5.0
Scored across 29 tools
Disambiguation5/5
Each tool targets a distinct resource and action, with clear differentiators: file upload vs update vs fetch, local vs URL sources, full-text vs prefix search, page vs revision vs pages. Even similar tools like get-file and get-file-data serve clearly different purposes (metadata/URL vs inline image).
Naming Consistency5/5
Tool names follow a consistent verb_noun (or verb-object) pattern throughout, e.g., delete-page, get-page-history, upload-file-from-url, create-page. Minor exceptions like whoami and parse-wikitext still fit the verb-object style, and singular/plural usage is consistent per resource (get-page vs get-pages).
Tool Count3/5
With 29 tools, the count exceeds the typical 3-15 range and is in the 'heavy' 16-25 zone or beyond. However, the breadth of wiki operations (page CRUD, file management, search, history, admin, OAuth, multi-wiki) justifies many of them, though some could potentially be consolidated.
Completeness4/5
The tool surface covers the full lifecycle for pages (create, read, update, delete, undelete, move) and files (upload, update, read, fetch), plus search, history, comparison, parsing, categories, links, recent changes, and site info. Minor gaps like page protection or watchlist management exist but are not essential for common wiki workflows.
Maintenance
ActivityActive
ResponsivenessWithin a week