MediaWiki MCP Server
An agent reads and edits pages of any MediaWiki wiki: search, history, files, categories and writing through OAuth
- 147 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Write tools can delete, move and protect pages
- OAuth tokens sit in a file on disk and edits are made in your name
Install
- Works in
Manual install
claude mcp add mediawiki-mcp-server -- npx -y @professional-wiki/mediawiki-mcp-server@latestReads public wikis without configuration.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Write tools can delete, move and protect pages
- OAuth tokens sit in a file on disk and edits are made in your name
This is third-party code. Review the repository files before installing.
What it does
MediaWiki MCP Server connects an agent to any wiki on the MediaWiki engine, from Wikipedia to a company knowledge base. Read tools: `get-page`, `get-pages` (up to 50 pages per call), `search-page` and prefix search, history and revisions, `compare-pages` for diffs, category members, backlinks, recent changes, wiki info and wikitext parsing without saving. Write tools are marked with a lock icon and need sign-in: creating, editing, moving, protecting, deleting and restoring pages, and uploading and replacing files from disk or by URL. Writes are refused on a wiki with `readOnly: true`, and if the flag is set on every connected wiki these tools are hidden from the list. Wikis are configured in `config.json` and every tool has an optional `wiki` argument. Sign-in goes through browser OAuth or credentials, and there are extension packs such as `neowiki-cypher-query`.
Who it is for. Editors and administrators of MediaWiki wikis who review, edit and move pages together with an agent.
Good fit when
- You need to find outdated pages in a company wiki by category and compare revisions
- Dozens of pages need one template change and the agent reads them in batches of up to 50
- A page must be moved to a new title with its history kept
- Reading Wikipedia or another public wiki works without sign-in and without any config
Not a fit when
- You need a mass import of thousands of pages: the server is built for dialogue with an agent and not for batch loading
- You only need read access to Wikipedia and the agent's built-in search is enough
- The wiki runs another engine such as Confluence or DokuWiki: the server talks to the MediaWiki API
Example request
Find all pages in the category Outdated in our wiki, show what changed in the latest revisions and compile an update listMCP
- Transport
- stdio, http
- Authentication
- OAuth
Environment variables
CONFIG- Path to `config.json` with wiki settings, default `config.json`.
MCP_OAUTH_NO_BROWSER- Value 1 skips opening a browser and prints the auth URL to stderr.
Limitations
Configuration is needed only for a private wiki or for write tools and everything else works without it. Write tools need wiki rights: create, edit and move, delete, protect, upload files. Sign-in uses browser OAuth with `oauth2ClientId` and `oauth2CallbackPort` or credentials, and OAuth tokens are stored in `~/.config/mediawiki-mcp/credentials.json`. The per-wiki `readOnly: true` mode blocks writes. If the server address is internal, links in a response are built from the public address and the internal host goes into `MCP_TRUSTED_HOSTS`. The license is MIT.
How to disable. Remove the server registration (`claude mcp remove mediawiki-mcp-server`), call `oauth-logout` to erase tokens and revoke the OAuth app in the wiki settings.
FAQ
How do I connect the server to Claude Code?
With `claude mcp add mediawiki-mcp-server -- npx -y @professional-wiki/mediawiki-mcp-server@latest`. For your own wiki add `-e CONFIG=path/to/config.json`.
Is sign-in needed for reading?
No, public wikis are read without sign-in and without a config file. Sign-in is needed for private wikis and for all write tools.
How do I stop the agent from writing?
Set `readOnly: true` on the wiki in `config.json`: writes will be refused and with the flag on every wiki the write tools disappear from the list.
Can I connect several wikis at once?
Yes, each one is set in the config and tools take a `wiki` argument with a key such as `en.wikipedia.org`. The `list-wikis` tool lists those connected.
How are tokens stored?
In `~/.config/mediawiki-mcp/credentials.json` on Linux and macOS and in `%APPDATA%\mediawiki-mcp\credentials.json` on Windows. `oauth-status` shows the state and `oauth-logout` erases tokens.
Discussion
No questions or reviews yet.
Related
MCP serversYandex Wiki MCP server
MCP-сервер Яндекс Вики
Yandex Wiki official MCP: an agent searches and reads knowledge base pages, builds summaries and creates new pages on behalf of the employee
An MCP server for Yandex Wiki with 30 tools: pages, attachments, comments, grids, page moves via clone, and deletion
Yandex Wiki MCP with grid table support
Yet Another Yandex Wiki MCP Server
An MCP server for the Yandex Wiki API with pages, attachments, token-based recovery, and a rare full toolset for dynamic tables (grids)
Yandex Wiki full-text search MCP server
Yandex Wiki Search MCP
An MCP server for Yandex Wiki: the same full-text search as the web UI, pages, comments, attachments and dynamic tables, 33 tools
MCP server for Yandex Wiki built on the ya-wiki-api package: 36 tools for pages, grids, attachments and a section-tree cache
A Python read-only Yandex Wiki MCP server where each user signs in through a browser form with an IAM token
README in short
Tool lists in tables: page reads, writes, wiki management, OAuth and extension packs. Then wiki resources, environment variables, configuration, sign-in methods, install for Claude Code, Codex and other clients, and HTTP deployment.