MCP Server by XWiki

XWiki MCP Server is a free, open-source, self-hostable extension that connects an XWiki knowledge platform to the AI agent of your choice. XWiki itself is a versatile knowledge platform for teams of all sizes, used to create wikis, documentation spaces, intranets, procedures and knowledge bases, where knowledge is organized in real time, collaborators work together, information is found faster and access is managed. The MCP Server adds a connection layer so that AI agents such as Claude Code, Codex, OpenCode, Pi, GitHub Copilot and MS Copilot — or anything else that speaks MCP — can work directly with that accumulated knowledge. Its stated purpose is to give your AI your wiki's knowledge while keeping the control: the extension is optional, installed by you and configured by you, rather than being a vendor-side feature that operates on your documentation without your say. The extension arrives at a specific moment for XWiki. XWiki has been around for over 20 years, which the team notes is plenty of time for organizations to build up a lot of knowledge in their wikis: documentation, internal procedures, and custom applications full of structured data. As AI agents become ingrained in daily workflows, the makers started thinking of ways to make all that internal knowledge available to them. The positioning is blunt: when knowledge grows, other tools start to break, and XWiki scales. A related problem raised in the launch discussion is that knowledge systems can eventually become write-only, and connecting them to an agent of choice may help surface what is already stored. The other half of the problem is control. The makers point out that Confluence announced this year that it will train AI on user documentation, something they completely disagree with, and that is why the XWiki MCP server keeps control in the hands of users, with the freedom to host as needed. Once an agent is connected, the first capability is reading. You can use the extension to query your knowledge base to get answers, so an agent can find out about an old project decision rather than a person digging through pages manually. Because the agent navigates the wiki with the same permissions as your user account, what it can see mirrors what you can see. Write, delete and page creation tools are destructive and are disabled by default, which the makers describe as the default starting point so no accidental oopsies happen; they can be turned on by ticking a box on the configuration page. That means a team can begin with read access, observe what the agent does with its wiki, and only later decide to allow changes. When write operations are enabled, the scope goes well beyond reading. The extension lets agents create and edit pages, update attached documents, and even build a small internal app. Since XWiki supports structured data, agents can work with objects and classes, not just read and write pages — the makers call this combination of XWiki and AI especially good for developers. Working with structured data means an agent is not limited to free text: it can operate on the data models that custom applications inside the wiki are built on. The launch description lists three things you can already do with the extension: query your knowledge base to get answers, create and edit pages, and work with structured data directly in XWiki. Control is enforced at several levels. The MCP endpoint is an OAuth protected resource: it advertises the XWiki OIDC Provider through the standard RFC 9728 metadata and a WWW-Authenticate header on a 401 response. Clients such as Claude Code or Claude Desktop discover it, run the normal OAuth authorization code flow against the OIDC Provider, and send a Bearer token; XWiki validates the token and the agent acts as that user, with that user's rights. The XWiki OIDC Provider extension must be installed for this. On the content side, XWiki has several deconflicting mechanisms: when collaborative editing is disabled, pages are locked while someone edits them; when collaborative editing is on, page saves are propagated to all users; if conflicts do appear, you choose whether to merge the changes or keep one or the other. Unlimited version history lets you revert a page to a previous version, and reverting restores the whole page — as a workaround for partial reverts you can preview any version and copy-paste changes into the latest version. Scripting capabilities, on top of being open source, make it possible to define and use your own deconflicting strategies. Overall, the product is an MCP server: an extension that speaks the Model Context Protocol, the interface through which AI agents call tools on an external system. Anything that speaks MCP can be connected, and the makers name Claude Code, Codex, OpenCode, Pi, GitHub Copilot and MS Copilot as examples. Installing it is a choice rather than a given: you decide if and when to install it, which model to connect through it, and where everything runs. You can self-host everything — XWiki, the MCP server and the AI model — if that is what you need. Because XWiki and the MCP server are fully open source, anything missing from the MCP layer is probably already doable through the REST API, which agents are described as quite good at using; if something is missing from the API, the open-source project can be extended or the changes contributed upstream. There is also a repository of skills and knowledge for agents (xwiki/xwiki-dev-llm on GitHub), an installation guide, source code on GitHub (xwiki-contrib/ai-llm) and feedback tracked on JIRA. The stated benefits follow from that design. Teams get an agent that can find out about an old project decision, update pages and attached documents, or build a small internal app, without exporting their knowledge to a third party. Discoverability and efficiency improve with the help of agents while the platform remains human-focused, which the makers describe as the focus: not turning the wiki into an agent-only system, but making what people wrote easier to reach. Documentation owners keep control rather than handing it to a vendor, and administrators keep the ability to run everything on their own infrastructure. Starting with read access gives a team room to see what the agent does with its wiki before enabling writes, and unlimited version history plus page-level conflict handling provide a route back if an agent edit goes wrong. Concrete scenarios named in the launch material include asking an agent about an old project decision recorded in the wiki, having it update pages, having it update attached documents, and having it build a small internal app. More broadly, XWiki is used to create wikis, documentation spaces, intranets, procedures and knowledge bases, and the MCP Server exposes that material to an agent of choice, so an organization's documentation, internal procedures and custom applications full of structured data become reachable by that agent. The makers also frame this as a fit for agentic workflows: one commenter noted they were using Confluence org-wide and that it was not coping with agentic workflows. The extension can be explored for use cases the team has not yet thought of, and the makers explicitly invite experimentation. The extension targets teams and organizations already using XWiki, and by extension any team that treats documentation as a long-lived asset — the wiki, intranet, procedure and knowledge base use cases XWiki serves. Named integrations are the AI agents themselves: OpenCode, Pi, Codex, Claude Code, GitHub Copilot and MS Copilot, plus anything else that speaks MCP. Two XWiki extensions are relevant: the XWiki OIDC Provider extension, required for the OAuth flow, and the MCP Server extension itself, installed and enabled as needed. The product is free and open source, listed with free options on Product Hunt and launched under Productivity, Open Source and Artificial Intelligence tags; the launch reached 175 upvotes and 38 comments with a #4 of the day badge for October 30th, 2026, while XWiki itself is rated 4.8 from 6 reviews. The takeaway is straightforward: XWiki MCP Server gives AI agents access to a wiki's knowledge — reading, writing and working with structured data — while every decision about installation, connection, hosting and permissions stays with the organization that owns the documentation. It is free, open source, optional and self-hostable, with destructive operations off by default and the agent bound to the rights of the connecting user. For teams whose knowledge has grown beyond what older tools can carry, that combination of reach and control is the point.