MediaWiki MCP Server

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

Feature

Tools

Resources

mcp://wikis/{wikiKey}

• Credentials (e.g., token, username, password) are never exposed in resource content.

• After add-wiki/remove-wiki, the server sends notifications/resources/list_changed so clients refresh.

Environment variables

Related MCP server: salesforce-mcp

Configuration

Note: Config is only required when interacting with a private wiki or using authenticated tools.

Create a config.json file to configure wiki connections. Use the config.example.json as a starting point.

Basic structure

Configuration fields

Wiki configuration fields

Authentication setup

For tools marked with 🔐, authentication is required.

Preferred method: OAuth2 Token

1. Navigate to Special:OAuthConsumerRegistration/propose/oauth2 on your wiki

2. Select "This consumer is for use only by [YourUsername]"

3. Grant the necessary permissions

4. After approval, you'll receive:

   • Client ID

   • Client Secret

   • Access Token

5. Add the token to your wiki configuration in config.json

Note: OAuth2 requires the OAuth extension to be installed on the wiki.

Fallback method: Username & Password

If OAuth2 is not available on your wiki, you can use bot credentials (from Special:BotPasswords ) instead of the OAuth2 token.

Installation

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

Follow the guide, use following configuration:

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.

Follow the guide, use following configuration:

Follow the Claude Code MCP docs.

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

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

Development

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

MCP Inspector

Test and debug the MCP server without a MCP client and LLM.

To start the development server and the MCP Inspector together:

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

MCPJam Inspector

Test and debug the MCP server, with a built-in MCP client and support for different LLMs.

To start the development server and the MCP Inspector together:

Test with MCP clients

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

1. Install the MCP server on your MCP client.

2. Change the command and args values as shown in the mcp.json file (or mcp.docker.json if you prefer to run the MCP server in Docker).

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

   npm run dev

Release process

To release a new version:

This command automatically:

• Updates package.json and package-lock.json

• Syncs the version in server.json and Dockerfile (via the version script)

• Creates a git commit

• Creates a git tag (e.g., v0.2.0)

1. Go to the Releases page

2. Click "Create a new release"

3. Select the tag you just pushed (e.g., v0.2.0)

4. Add a title and release notes

5. Click "Publish release"

The GitHub Actions workflow will automatically:

• Build and publish to NPM

• Publish to the MCP Registry

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 MIT License. See the LICENSE file for details.