EQVPS — pay Per Use V… vs MediaWiki MCP Server | AllMCPs
Side-by-Side Model Context Protocol Comparison
EQVPS — pay Per Use VPS for AI agents (API + MCP) vs MediaWiki MCP Server
In-depth architectural comparison of the EQVPS — pay Per Use VPS for AI agents (API + MCP) 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
EQVPS — pay Per Use VPS for AI agents (API + MCP)
Developer Tools · Remote HTTP/SSE
Quality: 52/100 (Good) | Auth: No auth required
MediaWiki MCP Server
Developer Tools · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose EQVPS — pay Per Use VPS for AI agents (API + MCP) if you need specialized Developer Tools tools running via a hosted cloud SSE transport. 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 EQVPS — pay Per Use VPS for AI agents (API + MCP) when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
EQVPS — pay Per Use VPS for AI agents (API + MCP) Tools (27)
list_plans
List available VPS plans with pricing, specs and OS images.
register_account
Create an EQVPS account (programmatic signup, no human in the loop). Returns a Bearer token.
login
Log in with email + password; returns a Bearer token.
whoami
Return the authenticated account profile.
get_balance
Return prepaid credit balance and currency.
topup_balance
Create a crypto top-up invoice; returns a checkout URL.
order_vps
Order a VPS by plan slug + OS id (pays from prepaid balance).
pay_invoice
Pay an owned unpaid invoice; returns a crypto checkout URL.
list_vps
List the account's VPS services (id, status, plan).
get_vps_status
Full detail for one VPS: status, specs, live VM state/uptime, SSH access.
power_vps
Power-control a VPS: start, stop or reboot.
set_hostname
Set the VPS hostname (DNS label; applied on reboot/rebuild).
+15 more tools listed on main page
MediaWiki MCP Server Tools (42)
compare-pages
Diff two versions of a wiki page by revision, title, or supplied wikitext.
get-category-members
List members of a category (up to 500 per call, paginated via `continueFrom`).
get-file
Fetch a file page.
get-file-data
Fetch a file's image bytes inline (base64) for visual analysis — for clients that can't reach the wiki host. Returns a scaled rendition (set `width`); non-renderable types (audio, video, binaries) error. For metadata or a download URL, use `get-file`.
get-links-here
List pages that reference a wiki page — pages that link to it, embed it as a template, or display it as a file (select via `type`), including pages that reach it through a redirect. Up to 500 per call, paginated via `continueFrom`.
get-page
Fetch a wiki page.
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).
EQVPS — pay Per Use VPS for AI agents (API + MCP) Configuration
EQVPS — pay Per Use VPS for AI agents (API + MCP) is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, MediaWiki MCP Server belongs to Developer Tools using local stdio subprocess. Select EQVPS — pay Per Use VPS for AI agents (API + MCP) when you need capabilities focused on developer tools and MediaWiki MCP Server when you require tools for developer tools.
List recent change events across the wiki, filterable by timestamp, namespace, user, tag, type, and hide flags (up to 50 per call, paginated via `continue`).
get-revision
Fetch a specific revision of a page.
get-site-info
Get a wiki's key settings: MediaWiki version, content language, title-case rules, namespaces, installed extensions, license, and (optionally) statistics.
list-wikis
List every configured wiki — its key, sitename, server, whether it is read-only or the default, whether it is reachable, which extension-gated tools work on it, and, for an OAuth-configured wiki, its authorization server. Disabled when fewer than two wikis are configured.