Configure the MCP Server
Steps
Set up this wiki's MCP endpoint and choose what it exposes. Read MCP User Permissions first: everything an agent can reach is bounded by the wiki user it connects as.
- Open the wiki's administration and go to "Other > MCP Server".
- Check that the section does not show "configuration not trusted". If it does, click "Reset the configuration and take ownership": the stored settings are dropped, the defaults apply, and the page is saved under your account. When the section itself is not displayed, a main-wiki administrator who also administers this wiki can reset its row in the farm dashboard.
- Check that the MCP server is enabled. A subwiki has its own "Enabled" checkbox; the main wiki's flag is set in the farm dashboard.
- Choose whether unauthenticated callers may use the endpoint. On a subwiki, tick "Allow Guest Access" (off by default); on the main wiki, use the "Guest access" column of the farm dashboard. Guests are served with the guest user's rights and get read tools only, and a request that presents failing credentials is always refused.
- Set the server name and description. The shipped name is XWiki; the wiki's pretty name is used only when the field is left blank. The description becomes the MCP initialization instructions, with a "call man first" hint appended.
- Select the tools this wiki exposes in the tool tree. Every non-write tool is selected by default and write tools are off; see Tool Policies. An empty selection falls back to the defaults, so turn the endpoint off instead if it should expose nothing.
- Decide whether the endpoint may return rendered content. "Allow Rendered Content" is on by default and lets get_document return HTML-rendered content, which executes the page's macros with the page author's rights, exactly as viewing the page does. Turn it off to restrict agents to raw wiki source.
- Copy the endpoint URL for your MCP client from the "MCP server URL" row: <server>/<webapp>/rest/wikis/<wikiId>/aiLLM/mcp, where the wiki id must be the exact, case-sensitive id of the wiki, or the endpoint answers 404.
- Save the configuration. The next request rebuilds the server with the new settings; saving on the main wiki refreshes every wiki.
- Check from an MCP client that the endpoint reports as connected. With OpenCode, opencode mcp list names the server and the URL it answered on.
FAQ
What endpoint URL do I give to users?
Build it as https://<server>/<webapp>/rest/wikis/<wikiId>/aiLLM/mcp, where <server> is the domain and possibly the port, <webapp> is the web application path (usually xwiki, empty at the root) and <wikiId> is the exact, case-sensitive id of the wiki (xwiki for the main wiki). The "MCP server URL" row and the dashboard's "Server URL" column copy it for you. A different case gives 404.
Do I need to restart the MCP Server for changes to take effect?
No restart is needed. Saving the configuration invalidates the cached server and the next request rebuilds it; a save on the main wiki refreshes every wiki, a save on a subwiki only that wiki.
What happens if the configuration page is not trusted?
Its values are not applied: the endpoint is off and the stored settings are not shown. Reset the configuration to take ownership; the stored settings are dropped and the defaults apply. The farm dashboard has a Reset button on each untrusted row you administer, which stays available when the wiki's own section is not displayed.
What does an empty value mean?
An empty field is read as unset: enabled, allowRenderedContent and allowGuest then use their defaults (enabled, allowed, refused), serverName falls back to the wiki's pretty name, and an empty tool list falls back to the default policy. To disable the endpoint, turn Enabled off rather than emptying the tool list.
