A
licenseA
qualityA
maintenanceMCP server for controlling Miro whiteboards with AI assistants. Create and manage stickies, shapes, frames, connectors, and more.
88
28
MIT
mediawiki-mcp-server
by olgasafonova
Related Servers
Alternatives to mediawiki-mcp-server
- AlicenseAqualityAmaintenanceMCP server for ProductPlan - enables AI assistants to interact with roadmaps, OKRs, and discovery features.503MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for Wiki.js integration, enabling AI assistants to create, read, update, delete, search, and move wiki pages via natural language.1MIT
- AlicenseAqualityAmaintenanceA 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
- FlicenseBqualityCmaintenanceA MCP server that allows you to search and retrieve content on any wiki site using MediaWiki with LLMs 🤖. wikipedia.org, fandom.com, wiki.gg and more sites using Mediawiki are supported!227-
- AlicenseNot gradedqualityDmaintenanceMCP server that provides tools to add to, search, and manage a wiki knowledge base, enabling AI chat tools to contribute and retrieve information from the wiki via natural language prompts.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that provides secure access to a serverless Markdown wiki on AWS, enabling AI assistants to read, search, and edit pages with space-level permission checks and Bedrock-powered semantic search.MIT
- 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
TDQS
A3.9/5.0
Scored across 43 tools
Disambiguation4/5
The descriptions are unusually explicit, using USE WHEN and NOT FOR clauses to route between near-pairs (get_page vs get_page_summary vs get_sections vs get_page_info; search vs search_in_page vs search_in_file; find_replace vs bulk_replace; get_related vs find_similar_pages). The single-vs-batch variants (get_external_links/get_external_links_batch, get_page_info/batch_get_pages_info) are clearly demarcated. The only residual ambiguity is the dense cluster of page-content readers where overlap is inherent.
Naming Consistency4/5
Almost everything follows a predictable mediawiki_verb_noun snake_case pattern (list_pages, get_revisions, check_links, find_replace). The main blemish is inconsistent placement of the 'batch' qualifier: batch_get_pages (prefix) versus get_external_links_batch (suffix). Naming is still highly readable and uniform overall.
Tool Count2/5
At 43 tools the surface is well beyond the 25+ threshold for 'too many,' and there is real redundancy: single-vs-batch duplicates (get_external_links/get_external_links_batch, get_page_info/batch_get_pages_info), four overlapping content readers, and four search variants. Each tool is individually reasonable, but the set could be consolidated substantially.
Completeness4/5
Coverage is broad: read/search/edit/replace, categories, moves, uploads, history, terminology and translation checks, and link auditing. Gaps are minor but notable — there is no page-delete or revision-revert/rollback tool, and no protection management. Agents can work around these, so it is not a blocking gap.
Maintenance
ActivityActive
ResponsivenessResponsive