xwiki-mcp

A Model Context Protocol server for XWiki. It gives an MCP-capable assistant read-only access to the spaces, pages and attachments that one XWiki account can see.

XWiki has announced an MCP server of its own, but at the time this was written it had not been released. Until it is, there is no supported way to point an assistant at an XWiki instance, which also leaves the knowledge module of every openDesk deployment out of reach.

This server uses the documented XWiki REST API, which every instance exposes under /rest.

Every tool in this server is read-only. There is no code path that creates, edits or deletes a page, and no tool that writes to disk or makes a request to any host other than the configured instance.

The server authenticates as one XWiki account and therefore sees exactly what that account sees. XWiki's own page and space rights remain the access boundary; this server does not widen them.

Responses are size-capped before they reach the assistant. A single response body is read up to a limit and then aborted, and long page content is truncated with an explicit [truncated] marker rather than silently cut.

• Node.js 20 or newer
• An XWiki instance reachable from the machine running the server
• An XWiki account whose password works against /rest

XWiki instances behind an SSO-only setup often have HTTP Basic authentication disabled on /rest. When that is the case, this server cannot authenticate, and it says so explicitly rather than failing vaguely: an unauthenticated REST call returns the login page with status 200, which the server reports as unauthorized.

Before setting anything up, check from a shell:

curl -u 'username:password' 'https://wiki.example.org/xwiki/rest/wikis?media=json'

JSON means this server will work. HTML means Basic authentication is not available and an administrator would have to enable it.

git clone https://github.com/Nraitschew/xwiki-mcp.git
cd xwiki-mcp
npm install
npm run build

The build writes an executable entry point to dist/index.js.

The server is configured through environment variables. The host application that starts the server passes them in.

A missing or malformed variable makes the server exit with a message on stderr that names the variable, rather than starting and failing on the first tool call.

Edit the MCP configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "xwiki": {
      "command": "node",
      "args": ["/absolute/path/to/xwiki-mcp/dist/index.js"],
      "env": {
        "XWIKI_URL": "https://wiki.example.org/xwiki",
        "XWIKI_USERNAME": "your-login",
        "XWIKI_PASSWORD": "your-password"
      }
    }
  }
}

Restart Claude Desktop afterwards.

claude mcp add xwiki \
  --env XWIKI_URL=https://wiki.example.org/xwiki \
  --env XWIKI_USERNAME=your-login \
  --env XWIKI_PASSWORD=your-password \
  -- node /absolute/path/to/xwiki-mcp/dist/index.js

The server speaks MCP over stdio. Start it with node dist/index.js and the three required environment variables set; any client that can spawn a stdio server will work.

Tool results are JSON.

XWiki addresses a page as Space.PageName, and a nested space as A.B.PageName. Two details are easy to get wrong, and this server handles both:

• A literal dot inside a name is escaped as \. in a reference. Splitting on every dot would break exactly the pages whose names contain one, such as release notes or dates. The parser here resolves the escapes.
• A reference may be fully qualified as wiki:Space.Page. The wiki part is a separate REST path segment, not a dot-separated one.

A bare page name with no space is rejected rather than guessed at, because guessing a space would silently read a different page. Always pass a reference that search_pages, list_spaces or list_pages_in_space returned.

A failing tool call returns a result marked as an error whose text starts with a stable machine code:

npx @modelcontextprotocol/inspector node dist/index.js

The MCP Inspector lists the tools and lets you call them by hand, which is the fastest way to confirm the URL, credentials and wiki name are right.

npm install
npm run typecheck
npm test
npm run build

The unit tests cover the configuration parsing and the reference grammar, which is the part most likely to break silently. They make no network requests, so they run anywhere.

• Read-only by design. Creating or editing pages is not implemented.
• Attachment contents are listed but not downloaded.
• get_page returns the page source in its stored syntax (usually xwiki/2.1), not rendered HTML or plain text.
• Objects, classes and comments attached to a page are not exposed.
• Search pages once with the requested limit rather than paging through a large result set.

• opendesk-mcp connects a whole openDesk instance, including this server's XWiki tools.
• openproject-mcp does the same for OpenProject.

Apache License 2.0. See LICENSE.

This project is not affiliated with or endorsed by the XWiki project or XWiki SAS. "XWiki" is a trademark of its respective owner and is used here only to describe what this software connects to.