weftai-mcp vs MediaWiki MCP Server
weftai-mcp is an MCP server published by tochi-mba. Marketplaces we read that list it: 1 (PyPI (MCP servers)). MediaWiki MCP Server is an MCP server published by ProfessionalWiki. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  weftai-mcp |  MediaWiki MCP Server |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 0.7.0 Downloads/month (PyPI): 3 623 Downloads/week (PyPI): 312 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.21.0 Forks (GitHub): 44 Stars (GitHub): 147 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.21.0 Downloads/month (npm): 5 544 Downloads/week (npm): 2 365 Forks (GitHub): 44 Stars (GitHub): 147 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | weftai-mcp | MediaWiki MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 147 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 44 (better) |
| Last release (differs) | 2026-10-28 (worse) | 2026-11-06 (better) |
| Where it runs (differs) | On your machine (weftai-mcp) | Remote server or your machine |
| Transport (differs) | Not stated | stdio, Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 18, secrets among them: 0 |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/tochi-mba/weftai | github.com/professionalwiki/mediawiki-mcp-server |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (3 h ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
weftai-mcp
Serve a weftai runtime over the Model Context Protocol.
MediaWiki MCP Server
MCP server enabling AI clients to interact with any MediaWiki wiki through standard tools
How to run each
weftai-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
MediaWiki MCP Server As a Claude Code plugin
/plugin marketplace add professionalwiki/mediawiki-mcp-server
/plugin install mediawiki-mcp-server@professional-wikiCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only MediaWiki MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of weftai-mcp publish no settings it asks for, so we do not compare settings.
What it can do: weftai-mcp · What it can do: MediaWiki MCP Server · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.