We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

Wikimedia Enterprise Docs

MCP server by Wikimedia Enterprise

Search Wikimedia Enterprise API guides, endpoint references and response models, with links back to the official docs.

No sign-in (No account or key needed)Streamable HTTP

Connect to Wikimedia Enterprise Docs

No sign-in needed. Connect with Wikimedia Enterprise Docs’s own URL:

https://enterprise.wikimedia.com/mcp

Paste it into any client that supports remote MCP servers. Your client talks to Wikimedia Enterprise directly, not through mcp.tc.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/wikimedia-enterprise-docs

About

Gives an assistant read access to the Wikimedia Enterprise API documentation. It covers the Snapshot, On-demand and Realtime APIs and Metadata. You can search guide sections, the changelog, pricing, endpoints and response models, fetch full pages, and read the exact request and response shape of an endpoint from the OpenAPI definition. Results include a URL on enterprise.wikimedia.com.

The server is a hosted Streamable HTTP endpoint at https://enterprise.wikimedia.com/mcp. It is read-only, calls no live Wikimedia Enterprise API and needs no sign-in or API key. Content is licensed CC-BY-SA-4.0.

What you can do

  • Full-text search across guides, changelog, pricing, endpoints and models
  • Fetch the full text of a guide, endpoint or response model
  • List every API endpoint, optionally filtered by tag
  • Get the exact request and response shape of one endpoint
  • Look up field names, status codes and paths by exact token

Tools 4

  • searchRead-only

    Full-text search over guides, changelog, pricing, endpoints and response models; returns ids for…

  • fetchRead-only

    Get the full text of one docs page, endpoint or schema by id from search.

  • list_endpointsRead-only

    List every API endpoint in reference order, optionally filtered by tag.

  • get_endpointRead-only

    Get the exact request and response shape of one endpoint from the OpenAPI definition.

Read from the live server on 17 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.

Example prompts

  • Search the Wikimedia Enterprise docs for how to download a snapshot

  • What does the reference_risk_score field mean?

  • List the realtime-articles endpoints in the Wikimedia Enterprise API

  • Show the request and response shape for the snapshot download endpoint

Set up

Every client connects to enterprise.wikimedia.com. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http wikimedia-enterprise-docs https://enterprise.wikimedia.com/mcp
  1. Start Claude Code and type /mcp. wikimedia-enterprise-docs should show as connected.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Customize → Connectors, click + Add, then Add custom connector.
  2. Name it Wikimedia Enterprise Docs and paste this URL:
https://enterprise.wikimedia.com/mcp
  1. Click Add. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://enterprise.wikimedia.com/mcp and click Add.
  2. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
  2. Enter a name for the server.
  3. Under Connection, paste https://enterprise.wikimedia.com/mcp as the server URL, then for authentication choose No authentication.
  4. Check I understand and want to continue, then select Create as a plugin.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "wikimedia-enterprise-docs": {
      "url": "https://enterprise.wikimedia.com/mcp"
    }
  }
}

VS Code

Or from a terminal:

code --add-mcp '{"name":"wikimedia-enterprise-docs","type":"http","url":"https://enterprise.wikimedia.com/mcp"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "wikimedia-enterprise-docs": {
      "type": "http",
      "url": "https://enterprise.wikimedia.com/mcp"
    }
  }
}

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "wikimedia-enterprise-docs": {
      "serverUrl": "https://enterprise.wikimedia.com/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add wikimedia-enterprise-docs --url https://enterprise.wikimedia.com/mcp

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.wikimedia-enterprise-docs]
url = "https://enterprise.wikimedia.com/mcp"

Gemini CLI

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

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

{
  "mcpServers": {
    "wikimedia-enterprise-docs": {
      "type": "http",
      "url": "https://enterprise.wikimedia.com/mcp"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://enterprise.wikimedia.com/mcp.

Embed

Show Wikimedia Enterprise Docs in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Wikimedia Enterprise Docs on mcp.tc](https://mcp.tc/i/wikimedia-enterprise-docs/badge.svg)](https://mcp.tc/i/wikimedia-enterprise-docs)
HTML
<a href="https://mcp.tc/i/wikimedia-enterprise-docs"><img src="https://mcp.tc/i/wikimedia-enterprise-docs/badge.svg" alt="Wikimedia Enterprise Docs on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/wikimedia-enterprise-docs.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/wikimedia-enterprise-docs" title="Wikimedia Enterprise Docs on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/wikimedia-enterprise-docs.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Wikimedia Enterprise Docs card to your site.

Markdown
Add the mcp.tc card for Wikimedia Enterprise Docs, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/wikimedia-enterprise-docs.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="wikimedia-enterprise-docs"><a href="https://mcp.tc/i/wikimedia-enterprise-docs">Wikimedia Enterprise Docs on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![Wikimedia Enterprise Docs on mcp.tc](https://mcp.tc/i/wikimedia-enterprise-docs/badge.svg)](https://mcp.tc/i/wikimedia-enterprise-docs)
```

Reference: https://mcp.tc/embed

Change history

We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 05:35 UTC.

Follow Wikimedia Enterprise Docs and we’ll email you when something changes.

  1. , Automatic check

    New version 1.2.5 (was 1.2.4). Reported by the server.

  2. , Automatic check

    New version 1.2.4 (was 1.2.3). Reported by the server.

  3. , Automatic check

    New version 1.2.2 (was 1.2.0). Reported by the server.

  4. , Automatic check

    New version 1.2.0 (was 1.1.20). Reported by the server.

  5. , Automatic check

    New version 1.1.20 (was 1.1.19). Reported by the server.

  6. , Automatic check

    New version 1.1.18 (was 1.1.17). Reported by the server.

  7. , Automatic check

    New version 1.1.17 (was 1.1.16). Reported by the server.

  8. , Automatic check

    1 tool changed.

    Details, 27 Oct 2026, 17:58 UTC

    Changed 1

    • searchoutput schema
  9. , Automatic check

    New version 1.1.15 (was 1.1.14). Reported by the server.

  10. , Automatic check

    New version 1.1.14 (was 1.1.13). Reported by the server.

  11. , Automatic check

    New version 1.1.12 (was 1.1.11). Reported by the server.

  12. , Automatic check

    New version 1.1.11 (was 1.1.10). Reported by the server.

  13. , Automatic check

    New version 1.1.10 (was 1.1.8). Reported by the server.

  14. , Automatic check

    Tracking started: 4 tools.

FAQ

Can I paste mcp.tc/i/wikimedia-enterprise-docs into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://enterprise.wikimedia.com/mcp, so your client talks to Wikimedia Enterprise Docs directly. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Wikimedia Enterprise Docs need an API key or a sign-in?

No. Wikimedia Enterprise Docs doesn’t ask for an account or key.

Is Wikimedia Enterprise Docs a remote or a local server?

Remote. Wikimedia Enterprise hosts it at https://enterprise.wikimedia.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can Wikimedia Enterprise Docs do?

It has 4 tools, including search, fetch and list_endpoints. You can Full-text search across guides, changelog, pricing, endpoints and models, fetch the full text of a guide, endpoint or response model and list every API endpoint, optionally filtered by tag.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Does mcp.tc track changes to Wikimedia Enterprise Docs?

Yes. Wikimedia Enterprise Docs’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read Wikimedia Enterprise Docs’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with Wikimedia Enterprise. This page was built from Wikimedia Enterprise Docs’s public metadata, last checked on 17 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.