wikipedia-mcp
Related Servers
Alternatives to wikipedia-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceAn MCP server that enables LLMs to search, summarize, and retrieve detailed information from Wikipedia across multiple languages. It supports automated fact-checking by allowing models to proactively verify factual claims using Wikipedia's database.52MIT
- AlicenseBqualityBmaintenanceA Model Context Protocol server that retrieves information from Wikipedia to provide context to LLMs, allowing users to search articles, get summaries, full content, sections, and links from Wikipedia.222,952 PyPI295MIT
- 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-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that retrieves and provides Wikipedia content for requested topics, enabling easy access to Wikipedia information directly through the Model Control Protocol.1-
- AlicenseNot gradedqualityAmaintenanceMCP server for searching and reading Wikipedia articles, including summaries, full text, targeted sections, nearby pages, and language editions.127 npm3Apache 2.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
TDQS
Scored across 22 tools
Every tool has a duplicate with the 'wikipedia_' prefix, making it impossible to tell them apart. The descriptions are identical, so agents cannot distinguish between e.g. get_sections and wikipedia_get_sections, leading to high misselection risk.
The original tools use a consistent verb_noun pattern (e.g., get_article, search_wikipedia), but the addition of 'wikipedia_' prefixed duplicates mixes conventions and creates redundant, awkward names like wikipedia_search_wikipedia. This inconsistency makes the API feel disorganized.
At 22 tools, the server is heavily over-inflated; each of the 11 unique operations is exposed twice. This doubles the cognitive load and suggests poor API design, even though the underlying feature count is reasonable.
For a read-only Wikipedia API, the unique tools cover the core operations well: search, retrieval, summaries, sections, links, coordinates, and related topics. Minor advanced features like page categories or edit history are missing, but the surface is largely complete for typical use.