MCP
The MCP endpoint (/mcp) lets AI clients such as Claude Code, VS Code or Cursor search, read and edit the wiki using the Model Context Protocol.
It is disabled by default. It uses the same personal API tokens and the same permissions as the REST API and the web interface, so an assistant can only see and do what the owner of its token can see and do in the browser. For scripts and integrations, see API.
An administrator can enable these settings under Admin > Configuration (/Admin/Config), in the Functionality group. Changes apply as soon as the configuration is saved, without restarting the wiki.
| Setting | Needed for |
| Enable API | Personal API tokens. MCP does not work without it. |
| Enable MCP | The /mcp endpoint. When it is off, /mcp returns 404. |
| Allow API Writes | The create_page and update_page tools. When it is off, they return an error and reading still works. |
Create a personal API token in your profile under API Tokens. The steps, and how to keep tokens safe, are described in API.
Without a token, the client can only read what an anonymous visitor can read, so get_page needs plainText, and get_page_revisions and reading a help page with get_wiki_syntax_help are not available. Writing always needs a token.
Always use HTTPS
Always use the https:// address of your wiki. When a request to http:// is redirected to HTTPS, some HTTP clients drop the Authorization header. The client then continues as anonymous, without any error.The MCP endpoint uses the HTTP transport and is available at /mcp, for example https://wiki.example.com/mcp. Add it to your AI client together with the Authorization header.
Keep tokens out of configuration files that are committed to source control.
Claude Code
claude mcp add --transport http tightwiki https://wiki.example.com/mcp --header "Authorization: Bearer YOUR_TOKEN"VS Code (.vscode/mcp.json)
{
"servers": {
"tightwiki": {
"type": "http",
"url": "https://wiki.example.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}Cursor (.cursor/mcp.json)
{
"mcpServers": {
"tightwiki": {
"url": "https://wiki.example.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}Other clients that support MCP over HTTP with custom headers can be configured in the same way.
Once connected, you can ask the assistant things like "Find the pages about backups and summarize them" or "Add a troubleshooting section to the Installation page".
| Tool | Description | Parameters (required in bold) |
| search_pages | Searches the wiki pages. | query, page |
| get_page | Gets a page as wiki markup, or as rendered plain text. | navigation, revision, plainText |
| get_page_revisions | Lists the revisions of a page, newest first. | navigation, page |
| list_namespaces | Lists the namespaces that contain at least one readable page. | None |
| list_namespace_pages | Lists the readable pages of a namespace. | name |
| list_tag_pages | Lists the readable pages that have a tag. | tag |
| get_wiki_syntax_help | Lists the wiki markup help pages, or returns one of them. | page |
| create_page | Creates a page. | name, body, changeSummary, description |
| update_page | Saves a new revision of a page. | navigation, revision, body, changeSummary, description |
create_page and update_page follow the same rules as writing through the REST API:
- A change summary is always required.
- update_page needs the revision the edit is based on, from get_page. If the page has changed since, nothing is saved and the error tells the current revision.
- Leaving out the description when updating keeps it.
- Pages cannot be renamed or deleted.
- Revisions saved through MCP have a change summary prefixed with [MCP], so they can be recognized in the page history and reverted like any other revision.
The write tools are always listed by the server, but return an error when Allow API Writes is off or when the client has no token.
Failures are reported to the client as tool errors, not as HTTP status codes. The exception is an invalid token, which is rejected with 401 before any tool runs.