MCP server for XWiki REST API — full-text Solr search + read/write tools for AI agents
If you already use Xwiki MCP, the xwiki mcp mcp server is the piece that lets your assistant work with it directly. MCP server for XWiki REST API — full-text Solr search + read/write tools for AI agents.
MCP server for XWiki REST API. Lets AI agents (Claude Code, Claude Desktop, etc.) search, read and write your wiki — with proper Solr full-text search, not the half-broken legacy endpoint most clients default to.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Read — The Read tool exposed by this serverConfiguration is passed through the environment: XWIKI_BASE_URL, XWIKI_AUTH_TYPE, XWIKI_USERNAME, XWIKI_PASSWORD, XWIKI_TOKEN, XWIKI_REST_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Installation goes through your MCP client rather than a global install: point it at xwiki-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Xwiki MCP's toolset — Read — is a fair guide to whether it matches your workflow. It is maintained by vitos73; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Read | The Read tool exposed by this server. |
{
"mcpServers": {
"xwiki": {
"command": "npx",
"args": ["xwiki-mcp"],
"env": {
"XWIKI_BASE_URL": "https://wiki.example.com",
"XWIKI_AUTH_TYPE": "basic",
"XWIKI_USERNAME": "your-username",
"XWIKI_PASSWORD": "your-password"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| XWIKI_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| XWIKI_AUTH_TYPE | Configuration value read at startup. | Optional |
| XWIKI_USERNAME | Configuration value read at startup. | Optional |
| XWIKI_PASSWORD | Configuration value read at startup. | Optional |
| XWIKI_TOKEN | Credential the server authenticates with. | Yes |
| XWIKI_REST_PATH | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.