Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MediaWiki API MCP Serversearch for articles about artificial intelligence"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MediaWiki API MCP Server
A Model Context Protocol (MCP) server that allows LLMs to interact with MediaWiki installations through the MediaWiki API as a bot user.
Features
Tools
The server provides various MCP tools with the wiki_ prefix:
Tool | Description |
Edit or create MediaWiki pages with comprehensive editing options | |
Retrieve page information and content | |
Parse page content with support for wikitext processing, HTML generation, metadata extraction, and advanced parsing features | |
Compare two pages, revisions, or text content to show differences between them | |
Move pages with support for talk pages, subpages, and redirects | |
Delete pages with support for talk pages, watchlist management, and logging | |
Undelete (restore) deleted MediaWiki pages with comprehensive restoration options | |
Search for pages using MediaWiki's search API with advanced filtering | |
Search using OpenSearch protocol for quick suggestions and autocomplete | |
Get overall site information including general info, namespaces, statistics, extensions, and more |
Installation
Clone the repository and checkout the
mainbranchInstall dependencies using UV:
Set up environment variables:
Usage
Running the Server
Or directly:
Configuration with Claude Desktop
Configuration File Location
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Template Configuration
Add to your Claude Desktop configuration file:
Configuration Instructions
Replace
/absolute/path/to/mediawiki-api-mcpwith the actual absolute path to this project directoryUpdate
MEDIAWIKI_API_URLwith your MediaWiki installation's API endpointSet
MEDIAWIKI_API_BOT_USERNAMEto your bot username (typically in formatYourUserName@YourBotName)Set
MEDIAWIKI_API_BOT_PASSWORDto the generated bot password from your wiki'sSpecial:BotPasswordspageCustomize
MEDIAWIKI_API_BOT_USER_AGENTwith appropriate contact information (optional)
Bot Password Setup
Create bot credentials at e.g.: http://mediawiki.test/index.php/Special:BotPasswords
Required permissions:
Basic rights: Read pages
High-volume editing: Edit existing pages, Create, edit, and move pages
Additional permissions as needed for your specific use case
Security Notes
Keep your bot credentials secure and never commit them to version control
Use the principle of least privilege when setting bot permissions
Monitor bot activity through your MediaWiki's logging interface
Consider using IP restrictions for additional security
Development
Technology Stack
MCP SDK: mcp >= 1.2.0 (using FastMCP pattern)
HTTP Client: httpx >= 0.27.0 for MediaWiki API calls
Data Validation: pydantic >= 2.0.0 for configuration models
Environment: python-dotenv >= 1.0.0 for configuration
Testing: pytest with pytest-asyncio for async testing
Code Quality: ruff for linting, mypy for type checking
Architecture
FastMCP server with
@mcp.tool()decoratorsSeparation of concerns: server → handler → client → MediaWiki API
AsyncIO throughout for non-blocking operations
Environment-based configuration for MediaWiki credentials
Client Layer (client.py and client_modules/)
Handles MediaWiki API authentication and requests
Manages CSRF tokens and session state
Provides typed methods for API operations
Tools Layer (tools/)
Defines MCP tool schemas using JSON Schema
Separated by functional area (edit, search)
Ensures all tools have
wiki_prefix
Handlers Layer (handlers/)
Implements actual tool logic
Handles argument validation and error handling
Returns properly formatted MCP responses
Server Layer (server.py and server_tools/)
Main MCP server orchestration
Routes tool calls to appropriate handlers
Manages configuration and client lifecycle
Project Structure
The project is organized into modular components for maintainability:
Running Tests
Run specific test modules, e.g.:
Code Quality
Error Handling
The server implements comprehensive error handling:
Configuration errors: Missing environment variables
Authentication errors: Invalid credentials or permissions
API errors: Network issues, invalid requests
Tool errors: Missing parameters, invalid arguments
All errors are returned as MCP TextContent responses for LLM visibility.
Security
Bot credentials are required for editing operations
All API requests include proper User-Agent headers
CSRF tokens are automatically managed
Input validation on all tool parameters