How to Use XWiki's MCP Server: The Beginner's Guide (First Connect, the Ask-Your-Wiki Lesson, and the Self-Host Arc)

How to Use XWiki's MCP Server: The Beginner's Guide

Your team's knowledge is trapped in a wiki, and your coding agent can't read it. You ask the agent to write the deploy runbook for your service, and it invents one from memory — because the real runbook is sitting in XWiki, three clicks away from a human and infinitely far from the agent. This how to use XWiki MCP server guide closes exactly that gap: XWiki SAS shipped an official MCP Server (BETA) extension, launched on Product Hunt on October 30, 2026, that plugs your wiki into any MCP-capable AI assistant so the agent reads your docs before it answers. Before you wire anything up, confirm the endpoint URL responds using our REST API tester — it takes thirty seconds and saves you from debugging the agent config when the problem was a typo in the URL.

What Is XWiki's MCP Server, Exactly?

XWiki's MCP Server is an official, free, open-source extension for the XWiki wiki platform that speaks the Model Context Protocol — the standard way for AI assistants to call tools. Once installed and authenticated, your coding agent can search your wiki's content (XWiki runs a Solr search behind the scenes), read pages, and — if you choose to enable them — create and edit pages, work with structured data, and handle attachments, all in plain natural language. The Product Hunt launch post, made by Gabriel, a product manager at XWiki, sums up the promise as "give your AI your wiki's knowledge while keeping the control." One detail to state once and remember: this is the official XWiki SAS extension, in BETA at version 0.10 (released September 18, 2026) — in short, an MCP server for wiki knowledge base access — and it is not the same thing as community MCP servers with similar names on GitHub, which I untangle below.

Why Is Your Wiki the Context Your Agent Is Missing?

Say this once and it will save you months of rework: your coding agent doesn't lack intelligence, it lacks your context. Without a connection to your wiki, every answer about your own systems comes from the model's training data — which is the opposite of your documentation. The MCP server hands the agent read access to your wiki, so "how do we deploy the billing service" is answered from the page your team actually wrote, not from a generic guess that happens to sound confident. That's what an XWiki AI assistant integration is really buying you: answers grounded in your own docs. The vendor's own launch examples make the same point: turn meeting notes into a formatted report, spread spreadsheets into wiki apps, or let the agent find the pages your team stopped updating — "wiki gardening" that never gets done by hand.

What Do You Need Before You Start?

Three things, and the order matters. The vendor's installation guide lists them as prerequisites, and every one is a separate extension or setting inside XWiki — not something you download from the web.

The extension runs on XWiki Cloud and on self-hosted instances, so either starting point works — if you're deciding between the two, our guide to what a VPS is covers the self-hosting side of the question. The current release is v0.10, shipped September 18, 2026 with attachment handling, structured-data tools, page deletion, navigation and history tools, backlink tools, an App Within Minutes reference page, a hidden flag on the write tools, search/RAG fixes, internationalization, and a server URL configuration field; v0.9 came in July 2026. Treat everything below as current for November 2026 — BETA means the moving parts move, so verify the exact screens against the official docs if something looks different.

How Do You Connect Your Coding Agent to XWiki?

You connect any MCP-capable client by giving it the server's endpoint URL and completing an OpenID Connect auth handshake. The endpoint pattern is documented in the official docs:

https://<server>/<webapp>/rest/wikis/<wikiId>/aiLLM/mcp

A real example: https://wiki.example.com/xwiki/rest/wikis/xwiki/aiLLM/mcp. Two details that break beginners most often: the wiki id is case-sensitive — xwiki for the main wiki, and the wrong case returns a 404 — and the agent's access is bounded by the wiki user it connects as, which is where the "keeping the control" part of the launch tagline comes from.

Here is the full first-connect arc, in order:

1. Install the "MCP Server (BETA)" extension from the XWiki Extension Manager.
2. Install the "OpenID Connect Provider" extension from the Extension Manager.
3. Open Administration → Other > MCP Server and finish the MCP Authentication setup.
4. Copy your instance's endpoint URL in the /rest/wikis/<wikiId>/aiLLM/mcp pattern and confirm it answers with the REST API tester.
5. Paste the URL into your agent's MCP configuration — the vendor's worked example is OpenCode, whose opencode.jsonc looks like this:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xwiki": {
      "type": "remote",
      "url": "https://xwiki.example.com/xwiki/rest/wikis/xwiki/aiLLM/mcp",
      "enabled": true
    }
  }
}

6. Complete the auth handshake from your terminal — in OpenCode that is opencode mcp auth xwiki — and sign in with your wiki account.
7. Ask a question only your wiki can answer (next section), and check that the answer cites a page.

That covers the "xwiki mcp server configuration" keyword end to end. For other clients, XWiki points to an "Assistant documentation links" page on xwiki.org with per-client config — the published snippet above is the OpenCode one, which is why it's the only client config shown here. The launch post also links the extension's source on GitHub and points contributors at JIRA for feedback — if you want to follow the project's development, our GitHub beginner guide will get you oriented. The launch announcement names OpenCode, Pi, Codex, Claude Code, and Microsoft Copilot as supported, plus any other tool that supports MCP — so if your goal is to connect Claude Code to XWiki, you're covered, and our Claude Code beginner guide will get you comfortable with the agent side first.

What's the First Query That Proves It Works?

Ask your agent a question it cannot answer from training data: "What does our wiki say about the on-call rotation?" or "Summarize the deploy runbook for the billing service." Then check where it actually read — the MCP server's tools hand the agent real page content, so the answer should reference a specific wiki page, not speak in generalities. If the agent answers fluently but cites nothing, the connection isn't live and you're back to generic guessing; fix the config before you trust any answer. This "ask your wiki" test is the whole point of the extension: the vendor's Product Hunt post says the agent inherits your permissions, so what it can read is exactly what you could read — nothing more, nothing less.

What Can Your Agent Actually Do With Your Wiki?

Out of the box, the agent reads: search across all wiki content, read pages, and pull attachments. Write tools exist — create and edit pages, page deletion, structured-data work with objects, classes, and App Within Minutes — but they are disabled by default, and an admin has to enable them deliberately. That's the security model in one sentence: read first, write only when you say so, and always inside the connecting user's own permissions.

The October 29, 2026 webinar — "Your wiki, your AI: Meet the XWiki MCP Server (BETA)", a 30-minute demo at 15:00 CET presented by Gabriel C. — walked through the flagship flows live: agents searching, reading, creating, and editing wiki content, working with structured XWiki data, and administrators controlling what the agents can reach and where the AI infrastructure runs. One vendor claim from the launch material deserves a flag rather than a fact: "tasks that would normally take you a couple of hours can now be done in a matter of minutes" is marketing, not a measured result — the real win is the error you avoid when the agent reads the actual doc.

How Do You Run It Next to Your Own XWiki?

The self-host arc is short because the extension lives inside XWiki itself — you don't run a separate server process. Install the extensions on your instance, run the authentication setup under Administration → Other > MCP Server, and expose your instance's HTTPS URL to the machine your agent runs on. The extension runs the same on XWiki Cloud and on a self-hosted instance; the decision is really about where your wiki lives. If it lives on your own machine, the official Docker image is the standard way to run XWiki — our Docker beginner guide walks through the container basics you'll need. Requests that present failing credentials are always refused, per the official docs — the server never degrades to anonymous access silently.

Access control is the part to get right on day one. Everything the agent can reach is bounded by the wiki user it connects as, so connect it as a purpose-made service user with exactly the spaces it needs — not as an administrator. Review which spaces that user can see before you run the auth handshake, because the agent inherits those permissions wholesale. Guest access exists for public read-only scenarios and is off by default; leave it off unless you have a genuine reason.

Which xwiki-mcp-server Is This?

A name collision worth exactly one paragraph, because it has already confused people: alfredfs85/xwiki-mcp-server on GitHub — a community Node.js/Express server with a Docker setup script, a .env file holding XWIKI_URL, XWIKI_USERNAME, and XWIKI_PASSWORD, listening on port 3000 with a /mcp endpoint and tools named search_xwiki, get_xwiki_page, and create_xwiki_page — is a separate, independent project, documented on DeepWiki roughly 217 days ago. It is not this product. This article is about the official XWiki SAS MCP Server (BETA) extension only; a second third-party entry, danimoya/xwiki-surgical-mcp listed on glama.ai, is likewise unrelated. If a tutorial shows you a .env file with a wiki password in it, you're reading the community project, not the official one.

6 Beginner Mistakes to Avoid With XWiki's MCP Server

Sources

Every fact above comes from a source fetched on November 3, 2026:

• XWiki, "Connect AI to your wiki through the XWiki MCP Server", xwiki.com, published October 25, 2026 — the official announcement: what the extension does, the OpenCode config example, the October 29 webinar.
• XWiki.org, "Configure the MCP Server" — official docs: the three prerequisites, the endpoint URL pattern, case-sensitive wiki id, Administration → Other > MCP Server, the credential-refusal behavior.
• XWiki.org news, MCP Server v0.10 release notes, September 18, 2026 — current version and its feature list (v0.9 released July 2026).
• Product Hunt, "MCP Server by XWiki", launched October 30, 2026 — posted by Gabriel, Product Manager at XWiki, hunted by @fmerian; tagline "Give your AI your wiki's knowledge while keeping the control"; 4.83/5 from 6 ratings at launch.
• LinkedIn "Next in AI" newsletter, October 30, 2026 — confirmation of the Product Hunt launch date.
• Zlio listing for XWiki MCP Server — 99 upvotes, listed price Free.
• LinkedIn XWiki September recap — webinar details: "Your wiki, your AI: Meet the XWiki MCP Server (BETA)", October 29, 2026, 15:00 CET, presented by Gabriel C.

Frequently Asked Questions

Is the XWiki MCP Server really free?

Yes — the Product Hunt launch describes it as a free, open-source extension, and Zlio lists its price as Free. Remember it is BETA software at version 0.10, so expect the config screens and tool list to keep evolving.

Does my agent get write access to my wiki?

Not by default. Read tools (search, read pages, attachments, navigation, history) are on; the create/edit/delete page tools are disabled until an admin enables them. And even then, everything the agent touches is bounded by the wiki user it connected as — it cannot reach what that user cannot reach.

What's the difference from the alfredfs85 xwiki-mcp-server on GitHub?

That's a separate community project — a Node.js/Express server you run yourself with your wiki credentials in a .env file, predating the official launch. The official product is an extension installed inside XWiki itself with OpenID Connect auth. If a guide shows you a wiki password in a config file, it's the community project.

Does it work with Claude Code? What about XWiki Cloud?

The launch announcement names OpenCode, Pi, Codex, Claude Code, and Microsoft Copilot as supported, plus any MCP-capable tool — XWiki's xwiki.org docs host per-client config links. It works on both XWiki Cloud and self-hosted instances; if you self-host, our Docker beginner guide covers running XWiki in a container.

Why not just paste wiki pages into the agent myself?

You can, for one page — but the MCP server searches the entire wiki through XWiki's Solr index, follows links and history, respects your permissions automatically, and always reads the current version. Pasting is a snapshot; the MCP connection is a live, permission-aware window into the wiki.