Side-by-Side Model Context Protocol Comparison
MediaWiki MCP Server vs Umd MCP
In-depth architectural comparison of the MediaWiki MCP Server and Umd MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MediaWiki MCP Server
Developer Tools · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Umd MCP
Developer Tools · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Verdict Summary: Choose MediaWiki MCP Server if you need specialized Developer Tools tools running via a local process. Choose Umd MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose MediaWiki MCP Server when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- You have access to required keys:
CONFIG, MCP_TRANSPORT, MCP_LOG_LEVEL, MCP_CONTENT_MAX_BYTES. - Primary tools included: get-page, get-pages, get-page-history.
U
Choose Umd MCP when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- You have access to required keys:
UMD_MCP_BROWSER, UMD_MCP_PROFILE_DIR, CANVAS_TOKEN. - Primary tools included: login, logout, whoami.
Feature & Specification Comparison
Tools & Capabilities Breakdown
MediaWiki MCP Server Tools (30)
get-page
Returns a single wiki page (wikitext source, rendered HTML, or metadata only). If the title does not exist, an error is returned. Use metadata=true to retrieve the revision ID (for edit-conflict detection), page size, and section outline. Set content="none" to fetch only metadata. Large content is truncated at 75000 bytes by default, with a marker reporting how much of it was returned and which sections a narrower read can target; a follow-up call with section=N fetches a specific section. For more than one page at a time, use get-pages. For a specific historical revision, use get-revision.
get-pages
Returns multiple wiki pages in one call (wikitext source or metadata only). Suited to reading a cluster of related pages, diffing a page family, or syncing pages to local storage. Accepts up to 50 titles; missing pages are reported inline (not as errors). One byte budget covers the whole response, 75000 bytes by default: pages come back whole in the order asked for until it is spent, and the pages past that point are named rather than returned, so a follow-up call for those names fetches the rest. Only a first page larger than the budget on its own is truncated, with a marker reporting how much of it was returned and which sections a narrower read can target. For a single page or HTML output, use get-page. requestedTitle is included only when it differs from the resolved title.
get-page-history
Returns revision metadata (revision ID, timestamp, user, comment, size, minor flag) for a wiki page, in segments of 20 revisions, newest first. Paginate with olderThan or newerThan (mutually exclusive). If the title does not exist, an error is returned. Boolean flags appear only when true.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
MediaWiki MCP Server Configuration
Umd MCP Configuration