Wikimedia Enterprise docs MCP Server

by wikimedia-enterprise Your server? Claim it

answering

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

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

Uptime history 4 days of history

4 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

664 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 8

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

18 Sep a tool changed version3 times that day

18 Sep 2 tool descriptions were rewritten fetch, search

16 Sep a tool changed version2 times that day

15 Sep a tool changed version

and 3 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.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add docs --transport http https://enterprise.wikimedia.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "docs": {
      "url": "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

{
  "mcpServers": {
    "docs": {
      "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

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

URL	Transport	State	Latency	Checked
https://enterprise.wikimedia.com/mcp	streamable-http	answering	677 ms	14 min ago

Alternatives to Wikimedia Enterprise docs

same job, measured the same way

EcoCarbonWiki

by carbonitex-ecogame

Read-only MCP for the Eco game wiki: search, Markdown pages, and wiki_* lookups. No keys, no writes.

10 tools answering

Private Law Wiki

by privatelawattorneys

Read-only answers and semantic search for wiki.private.law, served by the Mothership runtime.

5 tools answering

Obsidian Vault MCP Server

by oleksandrkucherenko

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

183 installs/wk local only

Agents Wiki

by agents-wiki

Public agent wiki: read-only search and article tools; authenticated write tools on /mcp/write.

5 tools answering

MediaWiki

by olgasafonova

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

local only

Commons Wikimedia

by pipeworx-io

Wikimedia Commons file/image/audio/video search via MediaWiki Action API

36 tools answering

wikiviews

by pipeworx-io

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

38 tools answering

Obsidian MCP Server

by cyanheads

Read, write, search, and surgically edit Obsidian notes, tags, and frontmatter via MCP.

7 553 installs/wk local only

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 664 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 with the file path 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 664 ms on average, which is faster than 18% 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.