MediaWiki MCP server with multi-wiki support and REST API
Most monitoring and observability work still happens through a UI a human drives. Mediawiki MCP server moves it into the conversation instead. MediaWiki MCP server with multi-wiki support and REST API.
A Model Context Protocol (MCP) server for MediaWiki instances with multi-wiki support. Uses the modern REST API (MediaWiki 1.42+) and Action API for full read/write access across multiple named wikis.
The server publishes 2 tools. What each one is for:
Prerequisites — The Prerequisites tool exposed by this serverCategories — The Categories tool exposed by this serverThe server ships on npm as mediawiki-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Configuration is passed through the environment: MEDIAWIKI_BASE_URL, MEDIAWIKI_MCP_HOST, MEDIAWIKI_MCP_PUBLIC_URL, OAUTH_TENANT_ID, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET, REDIS_URL, MEDIAWIKI_MCP_JWT_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mediawiki's toolset — Prerequisites, Categories — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Categories | The Categories tool exposed by this server. |
{
"mcpServers": {
"mediawiki-1": {
"command": "npx",
"args": ["-y", "mediawiki-mcp"],
"env": {
"MEDIAWIKI_BASE_URL": "your-value",
"MEDIAWIKI_MCP_HOST": "your-value",
"MEDIAWIKI_MCP_PUBLIC_URL": "your-value",
"OAUTH_TENANT_ID": "your-value",
"OAUTH_CLIENT_ID": "your-value",
"OAUTH_CLIENT_SECRET": "your-value",
"REDIS_URL": "your-value",
"MEDIAWIKI_MCP_JWT_SECRET": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| MEDIAWIKI_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| MEDIAWIKI_MCP_HOST | Endpoint or connection string the server talks to. | Optional |
| MEDIAWIKI_MCP_PUBLIC_URL | Endpoint or connection string the server talks to. | Yes |
| OAUTH_TENANT_ID | Configuration value read at startup. | Optional |
| OAUTH_CLIENT_ID | Configuration value read at startup. | Optional |
| OAUTH_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| REDIS_URL | Endpoint or connection string the server talks to. | Yes |
| MEDIAWIKI_MCP_JWT_SECRET | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.