Log inSubmit server
MediaWiki MCP Server logo

MediaWiki MCP Server

Connects MCP clients to MediaWiki for page search, reading, editing, file management, wiki administration, and OAuth.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MediaWiki MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mediawiki-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@professional-wiki/mediawiki-mcp-server@latest"
      ],
      "env": {
        "CONFIG": "YOUR_VALUE_HERE",
        "MCP_TRANSPORT": "YOUR_VALUE_HERE",
        "MCP_LOG_LEVEL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

MediaWiki MCP Server MCP server connects MCP clients to one or more MediaWiki wikis through standard read, search, write, file, and administration tools. It supports page content and metadata retrieval, revision history, diffs, recent changes, categories, backlinks, file data, and wikitext parsing. Authenticated users can create, edit, move, protect, delete, and restore pages, as well as upload files. Reach for it when an agent needs controlled access to MediaWiki knowledge bases, documentation sites, or multi-wiki content workflows.

Use cases

  • Search a MediaWiki knowledge base for related pages
  • Review revisions and compare proposed wiki changes
  • Update documentation pages with edit-conflict checks
  • Upload and inspect wiki files
  • Query structured data from supported MediaWiki extensions

Key features

  • Page, revision, history, and recent-change retrieval
  • Full-text and title-prefix search
  • Wikitext parsing and compact page diffs
  • Page editing, moving, protection, deletion, and restoration
  • Local and URL-based file uploads
  • Multi-wiki resources and extension-specific queries

Tools30

What MediaWiki MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~9.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

24/26 checks healthy over the last 91d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 1d ago via OSV.dev · @professional-wiki/mediawiki-mcp-server@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars147Stargazers on the source repository.
npm downloads7.5kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Tools exposed30Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How MediaWiki MCP Server works

What MediaWiki MCP Server does

MediaWiki MCP Server exposes MediaWiki operations as MCP tools for reading, searching, analyzing, and changing wiki content. Wiki tools can target a configured default wiki or another configured wiki by passing its key or resource URI. The server also publishes per-wiki MCP resources containing public connection details such as the site name, server address, article path, script path, privacy state, and read-only state.

Read operations cover individual pages, batches of up to 50 pages, historical revisions, revision metadata, recent changes, categories, backlinks, files, site configuration, and the authenticated identity. Search tools support full-text queries and title-prefix lookup.

Write tools cover page creation and updates, page moves, protection, deletion, undelete operations, and local or URL-based file uploads. Update operations include replacing content, appending, prepending, editing a section, and guarded find-and-replace changes. Edit-conflict checks can use the latest revision ID returned by a page read.

How it works

Responses provide prose in the MCP content channel and structured JSON in structuredContent. Large outputs use a default 75,000-byte limit and return markers that support narrower follow-up reads. List operations use their own caps and pagination cursors, including batches of 20 revisions, 50 recent changes, and up to 500 category or backlink results.

The server can register additional wikis from a URL and remove registered wikis, subject to wiki-management settings. Extension-specific tools appear only when the target wiki supports the relevant extension. Supported extension packs include NeoWiki, Semantic MediaWiki, Bucket, Cargo, and Wikibase, with tools for structured data, queries, schemas, entities, and extension tables.

Setup and configuration

The server uses stdio by default and can also use an HTTP MCP transport. CONFIG selects the configuration file and defaults to config.json; MCP_TRANSPORT selects stdio or http; and MCP_LOG_LEVEL controls logger severity. Wiki tools accept an optional wiki argument, while OAuth and wiki-management tools operate outside that per-call selection model.

OAuth status and logout are available only over stdio. OAuth status reports stored token scopes and expiry without exposing token values. Local file operations are restricted to configured upload directories, and supplied paths must be absolute paths inside an allowed directory.

Tools and capabilities

  • Read pages as wikitext, rendered HTML, or metadata.
  • Fetch page groups, revisions, change feeds, categories, backlinks, and file metadata.
  • Search full text or title prefixes and inspect namespaces, extensions, licenses, and statistics.
  • Preview wikitext, compare revisions, and retrieve renderable file data inline.
  • Create, update, move, protect, delete, and undelete pages when the authenticated account has the required rights.
  • Upload new files or file revisions from local paths or remote URLs.
  • Query supported NeoWiki, Semantic MediaWiki, Bucket, Cargo, and Wikibase installations.

Limitations and notes

Write operations depend on MediaWiki permissions and can fail for missing rights, conflicting revisions, nonexistent pages, or existing target titles. Deletion is soft deletion: revision history remains available for restoration until an administrator purges it. File data returned inline is limited to formats MediaWiki can rasterize; audio, video, and arbitrary binary files require the regular file metadata or URL tool. list-wikis is disabled when fewer than two wikis are configured, and wiki management can be disabled by configuration.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MediaWiki MCP Server

MediaWiki MCP Server is an MCP server that connects AI clients to MediaWiki wikis. Its main tools read, search, compare, parse, create, update, move, protect, delete, and restore pages, manage files, inspect wiki metadata, and query supported extensions such as Wikibase, Cargo, Semantic MediaWiki, NeoWiki, and Bucket.

Configure the server as an MCP endpoint using its configuration file and choose the stdio or HTTP transport with `MCP_TRANSPORT`. The default configuration path is `config.json`; `CONFIG` can point to another file.

Yes, it can target multiple configured wikis. Use `list-wikis` to discover wiki keys, pass a key or `mcp://wikis/<wikiKey>` URI through the `wiki` argument, or use `add-wiki` to register another wiki from its URL.

Pass the latest revision ID returned by a page read as `latestId` when calling `update-page`. The write is rejected if the page changed since that revision instead of silently overwriting the concurrent change.

Yes, it uploads new files or new revisions from local disk or remote URLs. Local paths must be absolute and inside a configured upload directory, and existing files require the update-file tools rather than the initial upload tools.

Related MCP servers

All in Knowledge & Memory All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMediaWiki MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mediawiki-mcp-server?style=directory)](https://allmcps.com/mcp/mediawiki-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/mediawiki-mcp-server"><img src="https://allmcps.com/api/badge/mediawiki-mcp-server?style=directory" alt="MediaWiki MCP Server on AllMCPs" /></a>