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.4324MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) Server for the mcp API.2,530 npmMIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) server for Wiki.js with hierarchical documentation & Docker setup50MIT

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.21990 npm1-- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol (MCP) server for converting files between different formats5MIT
- AlicenseNot gradedqualityBmaintenanceA generic, modular server for implementing the Model Context Protocol (MCP).299 npm45ISC
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) server implementation for Autodesk Maya120MIT
TDQS
Scored across 31 tools
Each tool targets a distinct resource+action and descriptions explicitly cross-reference siblings (create-page vs update-page, get-page vs get-pages vs get-revision, search-page vs search-page-by-prefix). The four file upload tools (upload-file, upload-file-from-url, update-file, update-file-from-url) and the get-file/get-file-data pair are the only near-overlaps, but each description disambiguates clearly ('initial upload' vs 'new revision', 'metadata/URL' vs 'inline image').
Almost everything follows a hyphenated verb_noun convention (get-page, create-page, delete-page, list-wikis, add-wiki, upload-file-from-url). The handful of exceptions — oauth-status, oauth-logout, whoami — are noun-first or one-word but still readable and clearly grouped, so it's a minor deviation rather than a break.
31 tools is above the comfortable range and four near-parallel file upload variants inflate the surface. The breadth (page lifecycle, files, links/categories, wiki registration, auth) makes the count defensible, but it's on the heavy side for what an agent must hold in context.
Coverage is strong: full page CRUD, soft delete/undelete, move, protect, history, revisions, diffs, search, categories, backlinks, files (read, inline, upload, update, URL variants), siteinfo, and multi-wiki/auth management. Minor gaps exist for user/contributions and watchlist-style operations, but core editing and reading workflows have no dead ends.