MediaWiki MCP Server

What is MediaWiki MCP Server about?

Provides an MCP server that bridges LLM clients with MediaWiki instances, exposing operations such as page retrieval, search, creation, and updates via standardized tool calls.

How to use MediaWiki MCP Server?

1. Install the server using npx:

   npx @professional-wiki/mediawiki-mcp-server@latest
   

2. Configure environment variables (e.g., CONFIG, MCP_TRANSPORT, PORT).
3. Register the server in your LLM client configuration (Claude Desktop, VS Code, Cursor, etc.) using the provided JSON snippets.
4. For authenticated operations, supply an OAuth 2.0 token obtained from the wiki’s OAuth extension.
5. Run the server (npm run dev for development, or start the compiled binary) and interact through the client’s tool interface.

Key features of MediaWiki MCP Server

• Tool set: create-page, update-page (OAuth‑protected), get-page, get-file, get-page-history, search-page, set-wiki.
• Supports both stdio and HTTP transports (MCP_TRANSPORT).
• Environment‑driven configuration with defaults (config.json, port 3000).
• Ready‑made installation paths for multiple environments (Smithery, Claude Desktop, VS Code, Cursor, Windsurf, Claude Code).
• Docker‑friendly development workflow (make dev).
• Integrated with the MCP Inspector for debugging.

Use cases of MediaWiki MCP Server

• Automated documentation: LLMs generate or update wiki pages based on code changes.
• Knowledge retrieval: Agents query wiki content to answer user queries with up‑to‑date information.
• Content migration: Scripts pull page histories and recreate them on another MediaWiki instance.
• File management: Retrieve and embed wiki‑hosted files within generated responses.
• Custom assistants: Build domain‑specific bots that interact with an organization's internal wiki.

FAQ from the MediaWiki MCP Server

Q: Do I need an OAuth token for all operations? A: Only the create-page and update-page tools require an OAuth 2.0 token. All read‑only tools work without authentication.

Q: Which transport should I choose? A: Use stdio for local LLM integrations (e.g., Claude Desktop). Choose http when the client expects a network endpoint.

Q: How do I change the wiki target at runtime? A: Call the set-wiki tool with the desired wiki URL; subsequent tool calls will operate on that wiki.

Q: Can I run the server inside Docker? A: Yes. Replace the npm command with make dev in the Docker container as described in the development section.

Q: Where is the configuration file located? A: By default, config.json in the working directory, but you can override the path with the CONFIG environment variable.

MediaWiki MCP Server

An MCP (Model Context Protocol) server that enables Large Language Model (LLM) clients to interact with any MediaWiki wiki.

Feature

Tools

🔐 Requires OAuth 2.0 token in configuration: Obtained via Special:OAuthConsumerRegistration/propose/oauth2 provided by the OAuth extension. Select "This consumer is for use only by UserName"

Name	Description
create-page 🔐	Create a new wiki page.
get-file	Returns the standard file object for a file page.
get-page	Returns the standard page object for a wiki page.
get-page-history	Returns information about the latest revisions to a wiki page.
search-page	Search wiki page titles and contents for the provided search terms.
set-wiki	Set the wiki to use for the current session.
update-page 🔐	Update an existing wiki page.

Environment variables

Name	Description	Default
CONFIG	Path to your configuration file	config.json
MCP_TRANSPORT	Type of MCP server transport (stdio or http)	stdio
PORT	Port used for StreamableHTTP transport	3000

Installation

To install MediaWiki MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @ProfessionalWiki/mediawiki-mcp-server --client claude

Follow the guide, use following configuration:

{
  "mcpServers": {
    "mediawiki-mcp-server": {
      "command": "npx",
      "args": [
        "@professional-wiki/mediawiki-mcp-server@latest"
      ]
    }
  }
}

code --add-mcp '{"name":"mediawiki-mcp-server","command":"npx","args":["@professional-wiki/mediawiki-mcp-server@latest"]}'

Go to Cursor Settings -> MCP -> Add new MCP Server. Name to your liking, use command type with the command npx @professional-wiki/mediawiki-mcp-server. You can also verify config or add command like arguments via clicking Edit.

{
  "mcpServers": {
    "mediawiki-mcp-server": {
      "command": "npx",
      "args": [
        "@professional-wiki/mediawiki-mcp-server@latest"
      ]
    }
  }
}

Follow the guide, use following configuration:

{
  "mcpServers": {
    "mediawiki-mcp-server": {
      "command": "npx",
      "args": [
        "@professional-wiki/mediawiki-mcp-server@latest"
      ]
    }
  }
}

Follow the Claude Code MCP docs.

Run the below command, optionally with -e flags to specify environment variables.

claude mcp add mediawiki-mcp-server npx @professional-wiki/mediawiki-mcp-server@latest

You should end up with something like the below in your .claude.json config:

"mcpServers": {
  "mediawiki-mcp-server": {
    "type": "stdio",
    "command": "npx",
    "args": [
      "@professional-wiki/mediawiki-mcp-server@latest"
    ],
    "env": {
      "WIKI_SERVER": "your.example.wiki",
      "OAUTH_TOKEN": ""
    }
  }
},

Development

🐋 Develop with Docker: Replace the npm run part of the command with make (e.g. make dev).

MCP Inspector

To start the development server and the MCP Inspector:

npm run dev

The command will build and start the MCP Proxy server locally at 6277 and the MCP Inspector client UI at http://localhost:6274.

Test with MCP clients

To enable your MCP client to use this MediaWiki MCP Server for local development:

1. Register the MCP server in your client config (e.g. claude_desktop_config.json for Claude Desktop). An example config is provided at mcp.json.

2. Run the watch command so that the source will be compiled whenever there is a change:

   npm run watch
   

Contributing

Contributions are welcome! Please feel free to submit a pull request or open an issue for bugs, feature requests, or suggestions.

License

This project is licensed under the GPL 2.0 License. See the LICENSE file for details.