← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionMediaWiki MCP ServerConnect AI clients to any MediaWiki through MCP.Firecrawl MCP ServerFirecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
FMRS69 / 100 · C75 / 100 · B
Reliability10 / 2013 / 20
Security and permissions14 / 2012 / 20
Maintenance13 / 2016 / 20
Documentation17 / 2017 / 20
Setup experience15 / 2017 / 20
Best for
  • Teams that need AI access to one or more MediaWiki wikis.
  • Users combining wiki retrieval with controlled content maintenance.
  • Users of Claude, Codex, VS Code, Cursor, or other listed MCP clients.
  • Scenarios needing clean, structured web context fed to an AI assistant
  • Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
Not for
  • Knowledge bases or content systems that do not use MediaWiki.
  • Workflows requiring writes without configuration or permissions.
  • Users expecting client or protocol compatibility that is not evidenced by the source.
  • Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
  • Sites that explicitly disallow automated access (robots.txt)
Required permissions
  • Read operations depend on the wiki being public or configured and reachable.
  • Write tools require the corresponding MediaWiki permissions; write tools are hidden from tools/list when the default wiki is read-only.
  • File uploads require allowed upload directories to be configured.
  • Cargo queries may require the runcargoqueries user right.
  • Private wikis and authenticated operations require OAuth, tokens, bot passwords, or another configured authentication method.
  • Requires a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
  • firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
Risks and side effects
  • In HTTP mode, Authorization Bearer tokens are forwarded to MediaWiki; authentication should be handled by a reverse proxy with TLS termination outside an untrusted network.
  • Before exposing HTTP to others, configure allowed hosts and origins to reduce DNS-rebinding and cross-origin risks.
  • Write, delete, move, and upload tools can change wiki content or files; use least-privilege credentials.
  • Outbound URL fetching and uploads are subject to SSRF and size limits; internal destinations require MCP_TRUSTED_HOSTS.
  • Tool responses have content, file-data, request-body, and upload size caps.
  • Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
  • firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
Supported clientsClaude Code, Codex, Claude Desktop, VS Code, Cursor, Antigravity, OpenCode, Devin Desktop, Zed, LM StudioClaude Desktop, VS Code, Cursor, Windsurf, Zed, Amp
Tools4611