Wiki over MCP
Read and edit the wiki from Claude Code, Cursor, VS Code or any other MCP client.
The DeutschlandGPT MCP server gives an AI client access to your wiki: list spaces, walk the page tree, search pages, read a page as Markdown, create pages and spaces, rewrite a body, move, rename, and send a page to the trash.
The same capabilities are available in the AI chat inside a wiki page. The only difference is where you sit: the MCP server brings the wiki into your development environment, the page chat brings the assistant to the page you have open.
Prerequisites
- The MCP server and the wiki have to be enabled for your organisation. If Settings → Connected apps shows no Connect an AI assistant card, ask your admin or support.
- Over MCP you see exactly the pages you can see in the wiki itself. Page sharing applies unchanged, so a client never sees more than you do.
- Creating a new space additionally needs the Create wiki spaces permission. Without it
wiki_createSpaceis refused and everything else keeps working.
Connect a client
Open Settings → Connected apps and copy the command or JSON snippet for your client from the Connect an AI assistant card. The URL shown there belongs to your own host, so use it instead of the example URL below.
Register the server in your client:
claude mcp add --transport http deutschlandgpt https://dialog.deutschlandgpt.de/mcp
On the first call the client opens the DeutschlandGPT sign-in. Sign in and confirm the consent screen. The client receives a token for exactly the permissions you pick there.
For the wiki, pick the tier you need: wiki.read to read, wiki.write to also create and edit,
wiki.manage to also move pages to the trash. A higher tier includes the lower ones, so
wiki.manage on its own is enough.
You can disconnect the client again at any time under Connected apps. Issued tokens stop working immediately.
Tools
Every page and every space can be addressed two ways: by its id, or by its /mnt/wiki/... path, which listSpaces and listPages return alongside the id. The two are interchangeable in every tool.
| Tool | What it does | Tier |
|---|---|---|
wiki_listSpaces | Lists the spaces you can see, with id, name and mount path. | wiki.read |
wiki_listPages | Returns one space's page tree in sidebar order, structure only. | wiki.read |
wiki_searchPages | Searches titles and content across every readable space, hits without an excerpt. | wiki.read |
wiki_getPage | Reads one page as Markdown, with breadcrumb and last-changed date. | wiki.read |
wiki_createSpace | Creates a new space, needs the Create wiki spaces permission. | wiki.write |
wiki_createPage | Creates a page under a space or a page, body as Markdown or HTML. | wiki.write |
wiki_updatePage | Replaces the body of an existing page, Markdown or HTML. | wiki.write |
wiki_movePage | Reparents or reorders a page and its children. Never changes content. | wiki.write |
wiki_renamePage | Changes the title of a page or a space, the body is untouched. | wiki.write |
wiki_deletePage | Moves a page and everything under it to the trash, where it can be restored. | wiki.manage |
wiki_deletePage is the only action that requires wiki.manage. It deletes nothing permanently and never empties the trash. A whole space cannot be deleted through it.
The chat inside a wiki page
The chat next to an open wiki page uses the same tools and additionally knows the page in front of you:
- It edits the open page directly: rewrite it, add to it, insert a table of contents.
- It reads any other page before quoting or summarising it.
- It creates new pages and spaces. The default parent is the space the current page lives in.
- It reparents, reorders and renames pages.
- It moves a page to the trash when you explicitly ask for that, and asks you to confirm first.
When you ask it to look something up without naming a source, it searches the wiki, not Outlook or another connected system.
Wiki content is stored as rich text, not as a Markdown file. Reading gives you a Markdown rendering of the page; writing takes the new body as Markdown or as HTML, exactly one of the two. A write replaces the whole page body and is merged with anyone editing the page in the browser at the same time. A very long page is truncated when read, and the result says so.