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.

Local serverstdioPython

What is the Mediawiki Api MCP MCP server?

A Model Context Protocol (MCP) server that allows LLMs to interact with MediaWiki installations through the MediaWiki API as a bot user. The mediawiki api mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Its toolset

Everything the assistant can do here goes through one of these:

  • Tools — The server provides various MCP tools with the wiki_ prefix:
  • Architecture — The Architecture tool exposed by this server

Configuration

You will need 4 environment variables: MEDIAWIKI_API_URL, MEDIAWIKI_API_BOT_USERNAME, MEDIAWIKI_API_BOT_PASSWORD, MEDIAWIKI_API_BOT_USER_AGENT. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mediawiki api mcp mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Mediawiki Api MCP's toolset — Tools, Architecture — is a fair guide to whether it matches your workflow. It is maintained by entanglr; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
ToolsThe server provides various MCP tools with the wiki_ prefix:
ArchitectureThe Architecture tool exposed by this server.

How to install the Mediawiki Api MCP MCP server

{
  "mcpServers": {
    "mediawiki-api": {
      "command": "uv",
      "args": [
        "--directory",
        "/absolute/path/to/mediawiki-api-mcp",
        "run",
        "mediawiki-api-mcp"
      ],
      "env": {
        "MEDIAWIKI_API_URL": "http://mediawiki.test/api.php",
        "MEDIAWIKI_API_BOT_USERNAME": "YourUserName@YourBotName",
        "MEDIAWIKI_API_BOT_PASSWORD": "YourBotPassword",
        "MEDIAWIKI_API_BOT_USER_AGENT": "MediaWiki-MCP-Bot/1.0 (your.email@mediawiki.test)"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
MEDIAWIKI_API_URLEndpoint or connection string the server talks to.Yes
MEDIAWIKI_API_BOT_USERNAMEConfiguration value read at startup.Optional
MEDIAWIKI_API_BOT_PASSWORDConfiguration value read at startup.Optional
MEDIAWIKI_API_BOT_USER_AGENTConfiguration value read at startup.Optional

Example prompts to try

  • Use Mediawiki Api MCP to Tools.
  • Use Mediawiki Api MCP to Architecture.

Frequently asked questions

It connects Mediawiki Api MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Tools, Architecture) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Mediawiki Api MCP directly.