MediaWiki▌
by professionalwiki
Integrate with MediaWiki via REST API for searching, content retrieval, file info, revisions, and page management with d
Integrates with MediaWiki instances through REST API to enable searching pages, retrieving content in multiple formats, accessing file information, viewing revision history, and performing authenticated operations like creating and updating pages with automatic wiki discovery and dynamic configuration management.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Content creators managing wiki documentation
- / Developers building wiki integrations
- / Organizations maintaining internal wikis
- / Researchers accessing MediaWiki data
capabilities
- / Search wiki pages by title and content
- / Retrieve page content and revision history
- / Create and update wiki pages
- / Upload files to wikis
- / Manage multiple wiki instances
- / Access file information and downloads
what it does
Connects to MediaWiki instances (like Wikipedia) to search, read, create, and edit wiki pages through the REST API. Supports multiple wikis with automatic discovery and authenticated operations.
about
MediaWiki is a community-built MCP server published by professionalwiki that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate with MediaWiki via REST API for searching, content retrieval, file info, revisions, and page management with d It is categorized under productivity. This server exposes 16 tools that AI clients can invoke during conversations and coding sessions.
how to install
You can install MediaWiki in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
MediaWiki is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
MediaWiki MCP Server
An MCP (Model Context Protocol) server that enables Large Language Model (LLM) clients to interact with any MediaWiki wiki.
Feature
Tools
| Name | Description | Permissions |
|---|---|---|
add-wiki | Adds a new wiki as an MCP resource from a URL. | - |
create-page 🔐 | Create a new wiki page. | Create, edit, and move pages |
delete-page 🔐 | Delete a wiki page. | Delete pages, revisions, and log entries |
get-category-members | Gets all members in the category | - |
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. | - |
get-revision | Returns the standard revision object for a page. | - |
remove-wiki | Removes a wiki resource. | - |
search-page | Search wiki page titles and contents for the provided search terms. | - |
search-page-by-prefix | Perform a prefix search for page titles. | - |
set-wiki | Sets the wiki resource to use for the current session. | - |
undelete-page 🔐 | Undelete a wiki page. | Delete pages, revisions, and log entries |
update-page 🔐 | Update an existing wiki page. | Edit existing pages |
upload-file 🔐 | Uploads a file to the wiki from the local disk. | Upload new files |
upload-file-from-url 🔐 | Uploads a file to the wiki from a web URL. | Upload, replace, and move files |
Resources
mcp://wikis/{wikiKey}
- Credentials (e.g.,
token,username,password) are never exposed in resource content. - After
add-wiki/remove-wiki, the server sendsnotifications/resources/list_changedso clients refresh.
{
"resources": [
{
"uri": "mcp://wikis/en.wikipedia.org",
"name": "wikis/en.wikipedia.org",
"title": "Wikipedia",
"description": "Wiki "Wikipedia" hosted at https://en.wikipedia.org"
}
]
}
</details>
<details><summary>Example read result</summary>
{
"contents": [
{
"uri": "mcp://wikis/en.wikipedia.org",
"mimeType": "application/json",
"text": "{ "sitename":"Wikipedia","server":"https://en.wikipedia.org","articlepath":"/wiki","scriptpath":"/w","private":false }"
}
]
}
</details>
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 |
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
{
"defaultWiki": "en.wikipedia.org",
"wikis": {
"en.wikipedia.org": {
"sitename": "Wikipedia",
"server": "https://en.wikipedia.org",
"articlepath": "/wiki",
"scriptpath": "/w",
"token": null,
"username": null,
"password": null,
"private": false
}
}
}
Configuration fields
| Field | Description |
|---|---|
defaultWiki | The default wiki identifier to use (matches a key in wikis) |
wikis | Object containing wiki configurations, keyed by domain/identifier |
Wiki configuration fields
| Field | Required | Description |
|---|---|---|
sitename | Yes | Display name for the wiki |
server | Yes | Base URL of the wiki (e.g., https://en.wikipedia.org) |
articlepath | Yes | Path pattern for articles (typically /wiki) |
scriptpath | Yes | Path to MediaWiki scripts (typically /w) |
token | No | OAuth2 access token for authenticated operations (preferred) |
username | No | Bot username (fallback when OAuth2 is not available) |
password | No | Bot password (fallback when OAuth2 is not available) |
private | No | Whether the wiki requires authentication to read (default: false) |
Authentication setup
For tools marked with 🔐, authentication is required.
Preferred method: OAuth2 Token
- Navigate to
Special:OAuthConsumerRegistration/propose/oauth2on your wiki - Select "This consumer is for use only by [YourUsername]"
- Grant the necessary permissions
- After approval, you'll receive:
- Client ID
- Client Secret
- Access Token
- Add the
tokento your wiki configuration inconfig.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
<details><summary><b>Install via Smithery</b></summary>To install MediaWiki MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @ProfessionalWiki/mediawiki-mcp-server --client claude
</details>
<details>
<summary><b>Install in Claude Desktop</b></summary>
Follow the guide, use following configuration:
{
"mcpServers": {
"mediawiki-mcp-server": {
"command": "npx",
"args": [
"@professional-wiki/mediawiki-mcp-server@latest"
],
"env": {
"CONFIG": "path/to/config.json"
}
}
}
}
</details>
<details><summary><b>Install in VS Code</b></summary>
code --add-mcp '{"name":"mediawiki-mcp-server","command":"npx","args":["@professional-wiki/mediawiki-mcp-server@latest"]}'
</details>
<details>
<summary><b>Install in Cursor</b></summary>
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"
],
"env": {
"CONFIG": "path/to/config.json"
}
}
}
}
</details>
<details>
<summary><b>Install in Windsurf</b></summary>
Follow the guide, use following configuration:
{
"mcpServers": {
"mediawiki-mcp-server": {
"command": "npx",
"args": [
"@professional-wiki/mediawiki-mcp-server@latest"
],
"env": {
"CONFIG": "path/to/config.json"
}
}
}
}
</details>
<details>
<summary><b>Install in Claude Code</b></summary>
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": {
"CONFIG": "path/to/config.json"
}
}
},
</details>
Development
🐋 Develop with Docker: Replace the
npm runpart of the command withmake(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:
npm run inspector
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:
npm run mcpjam
Test with MCP clients
To enable your MCP client to use this MediaWiki MCP Server for local development:
- Install the MCP server on your MCP client.
- Change the
commandandargsvalues as shown in themcp.jsonfile (ormcp.docker.jsonif you pre
FAQ
- What is the MediaWiki MCP server?
- MediaWiki is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for MediaWiki?
- This profile displays 75 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.7 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.7★★★★★75 reviews- ★★★★★Evelyn Huang· Dec 20, 2024
MediaWiki is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Shikha Mishra· Dec 8, 2024
Strong directory entry: MediaWiki surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Soo Anderson· Dec 8, 2024
I recommend MediaWiki for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Kwame Martin· Dec 4, 2024
We evaluated MediaWiki against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Rahul Santra· Nov 27, 2024
MediaWiki is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Aarav Farah· Nov 27, 2024
We evaluated MediaWiki against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Hiroshi Brown· Nov 23, 2024
I recommend MediaWiki for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Aanya Smith· Nov 11, 2024
Strong directory entry: MediaWiki surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Pratham Ware· Oct 18, 2024
We evaluated MediaWiki against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Aarav Liu· Oct 18, 2024
MediaWiki is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
showing 1-10 of 75