mediawiki-mcp
Related Servers
Alternatives to mediawiki-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceA secure MCP server for interacting with MediaWiki instances, allowing users to search, read, create, and manage wiki content like pages, categories, and files. It supports both public and private wikis with comprehensive authentication for full read and write operations.19AGPL 3.0
- AlicenseAqualityAmaintenanceMCP server for MediaWiki wikis. Search, read, edit, and manage wiki content from AI assistants. Includes formatting, link checking, revision history, and markdown conversion.4320MIT
- FlicenseNot gradedqualityDmaintenanceMCP server providing live Wikipedia recent changes feed, page summaries, trending pages, and Wikidata entity lookup.-
- AlicenseNot gradedqualityBmaintenanceMCP server for Wiki.js with full GraphQL API coverage, fine-grained permissions, multi-user support, and deployable on Vercel.Apache 2.0
- 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.9 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server for managing Wiki.js 2.x pages through its GraphQL API, enabling search, read, create, update, move, delete, version history, and asset listing.1316 npmMIT
TDQS
Scored across 21 tools
The three search/locate tools (find-page, search-page, search-page-by-prefix) have overlapping purposes and could be confused. While descriptions attempt to differentiate them, an agent may struggle to choose the right one. Other tools are clearly distinct.
All tool names follow a consistent verb-noun pattern with hyphens (e.g., list-wikis, get-page, upload-file). Verbs are predictable and there are no mixed naming conventions.
With 21 tools, this is on the heavier side, but the broad scope of MediaWiki management (wiki instances, pages, history, categories, files, recent changes) justifies the count. Each tool covers a distinct aspect of the domain.
Core workflows are well covered: page CRUD, history, file upload, category browsing, and search. Minor gaps exist (e.g., no page move/rename, no revision diff tool), but agents can work around them for most tasks.