mcpbeat Sign in

Wikimedia Enterprise docs MCP Server

by wikimedia-enterprise Your server? Claim it
answering

Wikimedia Enterprise docs is answering right now. Last checked 9 min ago. It exposes 4 tools.

Wikimedia Enterprise API docs: search the guides, read every endpoint. Read-only, no account needed.

Uptime history 49 days of history
49 days agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
517 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 23

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 September 2026. No other catalogue keeps this.

2 Nov a tool changed version
30 Oct a tool changed version
29 Oct a tool changed version
27 Oct a tool changed version
21 Oct a tool changed version2 times that day
19 Oct a tool changed version
13 Oct a tool changed version2 times that day
8 Oct a tool changed version
7 Oct a tool changed version2 times that day
6 Oct a tool changed version2 times that day
and 13 more, back to 15 September 2026

Nothing serious here today

Today is the operative word: we check Wikimedia Enterprise docs every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add docs --transport http https://enterprise.wikimedia.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://enterprise.wikimedia.com/mcp
~/.codex/config.toml
[mcp_servers.docs]
url = "https://enterprise.wikimedia.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "docs": {
      "url": "https://enterprise.wikimedia.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "docs": {
      "type": "http",
      "url": "https://enterprise.wikimedia.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

endpoint
get_endpoint
The exact request and response shape of one endpoint, dereferenced from the OpenAPI definition (the source of truth), as structured JSON plus a markdown rendering. Identify it by `operationId`, or by `method` and `path`.
endpoints
list_endpoints
Every endpoint in the Wikimedia Enterprise OpenAPI definition, in reference order, with its technical title, its plain-language line and a link into the reference. Filter with a tag: authentication, codes, languages, projects, namespaces, batches, wikidata-batches, snapshots, wikidata-snapshots, structured-snapshots, articles, structured-contents, wikidata, realtime-articles, realtime-wikidata.
fetch
fetch
Full text for one id from `search`: `docs/<slug>` (a guide, as markdown; a `#section` suffix is accepted; `docs/changelog` is the release notes and `docs/pricing` the plans), `op/<operationId>` (one endpoint rendered from the OpenAPI definition) or `schema/<name>` (one response model).
search
search
Full-text search over the Wikimedia Enterprise API documentation: guide sections, the changelog, pricing, endpoints and response models. Exact tokens work best (a field name such as `reference_risk_score`, a status code such as `429`, or a path such as `/v2/snapshots/{identifier}/download`); plain questions work too. Returns ids to pass to `fetch`.

Endpoints

URLTransportStateLatencyChecked
https://enterprise.wikimedia.com/mcp streamable-http answering 496 ms 9 min ago

Alternatives to Wikimedia Enterprise docs

same job, measured the same way
Wikipedia MCP
by mrfentmen

Search Wikipedia, fetch article summaries, and get random articles from the Wikimedia REST API....

65 installs/wk local only
Obsidian Notes
by moreno-omar

Search an Obsidian vault by tag, term and wikilink graph. Read-only, deterministic, no embeddings.

local only
Obsidian Vault MCP Server
by oleksandrkucherenko

Access Obsidian vaults via Local REST API - read, search, and interact with notes

162 installs/wk local only
tavya
by tavya

Run and manage AI agent tasks on tavya: create, search and steer tasks, read wikis, call the API.

answering
Vitextra Knowledge Base
by vitextra

Search and read Vitextra docs, product pages, how-to guides and FAQ.

4 tools answering
Mitre Attack MCP
by mrfentmen

Search the MITRE ATT&CK enterprise knowledge base for adversary techniques and tactics.

63 installs/wk local only
MediaWiki
by olgasafonova

Search, read, and edit any MediaWiki wiki. Works with Wikipedia, Fandom, and more.

local only
Wikiviews
by pipeworx-io

Wikiviews MCP — wraps the Wikimedia Pageviews API (free, no auth)…

202 installs/wk 47 tools answering

Wikimedia Enterprise docs — questions

Answers built from our own checks of this server.

What can Wikimedia Enterprise docs do?
It exposes 4 tools, read directly from the server on our last check. Among them: fetch, get_endpoint, list_endpoints, search. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Wikimedia Enterprise docs working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 517 ms. The bar chart above shows every period we have measured.
How do I connect Wikimedia Enterprise docs?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Wikimedia Enterprise docs need an API key?
No. Wikimedia Enterprise docs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Wikimedia Enterprise docs?
It answers our handshake in 517 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.