Side-by-Side Model Context Protocol Comparison
Affset vs MediaWiki MCP Server
In-depth architectural comparison of the Affset and MediaWiki MCP Server 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
Affset
Developer Tools · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
MediaWiki MCP Server
Developer Tools · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Affset if you need specialized Developer Tools tools running via a local process. Choose MediaWiki MCP Server 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 Affset 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).
- Primary tools included: whoami, get_stats, list_campaigns.
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).
- Primary tools included: compare-pages, get-category-members, get-file.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Affset Tools (29)
whoami
Show the tenant this server is bound to: namespace, API base, derived dashboard URL, and (when readable) company / timezone / custom API domain. Read-only.
get_stats
Traffic stats grouped by a dimension (date, campaign, zone, country, sub1–5, advertiser, publisher, …), optionally narrowed with `advertiser_email`/`publisher_email` filters (one user, any group_by). Returns clicks, conversions, CR, payout, media cost and ROI as a table. `paid_only` defaults to tru…
list_campaigns
List campaigns (status / name filter, pagination).
get_campaign
One campaign's full record — every field (untruncated offer URL, exact schedule, budgets/pacing, silent flag, payout goal type) plus its targeting rules and payout rules, in one call.
list_zones
List traffic-source zones (status / name filter, pagination, linked source).
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).
Affset Configuration
MediaWiki MCP Server Configuration