mediawiki-mcp-server
Related Servers
Alternatives to mediawiki-mcp-server
- AlicenseAqualityAmaintenanceMCP server for MediaWiki wikis. Search, read, edit, and manage wiki content from AI assistants. Includes formatting, link checking, revision history, and markdown conversion.4319MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) Server for the mcp API.1,877 npmMIT
- AlicenseNot gradedqualityFmaintenanceModel Context Protocol (MCP) server for Wiki.js with hierarchical documentation & Docker setup48MIT

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.1944 npm1-- 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).43 npm45ISC
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) server implementation for Autodesk Maya104MIT
TDQS
Scored across 30 tools
Each tool targets a distinct resource/action combination: page operations (create/update/delete/move/undelete), file operations (upload/update/get), wiki management (add/remove/list), and query tools (search, category members, links here, recent changes). Even closely related tools like get-page vs get-pages vs get-revision have clearly separated roles described in their docs.
All tools follow a consistent verb-noun pattern with hyphenated lowercase (protect-page, get-page-history, upload-file-from-url). Even exceptional names like 'whoami' and 'oauth-status' are standard and don't break the overall pattern.
30 tools is above the typical 3-15 range, but the server covers a broad MediaWiki surface: pages, files, wikis, site info, categories, links, recent changes, and auth. Each tool is non-redundant and serves a distinct purpose, so the count is justified for the domain's complexity.
The toolset provides full lifecycle coverage: page CRUD (create/get/update/delete/undelete/move), file management (upload/update/get), wiki management (add/remove/list), plus query and utility tools (search, history, compare, parse, protect, site info, category members, links here, recent changes, auth). No obvious dead ends or missing operations for common MediaWiki workflows.