Q.wiki MCP Server – Overview & Endpoint

Modified on Fri, 5 Jun at 4:05 PM

This article explains what the Q.wiki MCP Server is, what it can do, and how to find the endpoint URL for your Q.wiki instance.

Beta: The Q.wiki MCP Server is currently in beta. Features and availability may still change.

What is MCP?

The Model Context Protocol (MCP) is an open standard that allows AI tools such as Microsoft Copilot, ChatGPT, or Claude to access your Q.wiki content in real time.

What the Q.wiki MCP Server can do (Tools)

Feature	What the connected agent can do with it
Full-text search	Search across all modules – processes, work instructions, documents, glossary.
Page retrieval with metadata	Retrieve complete Q.wiki pages including page owner, status, and last approval date.
Roles & responsibilities	Deliver roles with name and description (not just IDs), look up individual roles by ID, retrieve recently edited pages for a role – e.g. for questions like "What are the current topics in my area of responsibility?"
File pages & attachments	Content from attached files is included in search results.
Read comments	The agent can include existing discussions in its responses.
Write comments	The agent can post feedback or notes as a comment in Q.wiki (optional; requires write permissions during authentication).

Good to know: The MCP Server only returns content that the authenticated user can already read directly in Q.wiki. Existing permissions are fully enforced.

Prerequisites

The "API / MCP" add-on module is booked and activated for your Q.wiki instance.

Important: Without the "API / MCP" add-on module, you cannot activate an MCP endpoint. You can request the module via the request form on modell-aachen.de (external).

Finding your MCP URL

Once the add-on module is activated, the MCP Server is automatically available at the following URL:

https://<tenant>.qwikinow.de/external-api/v1/mcp

Replace <tenant> with the name of your Q.wiki instance. You can find and copy the URL directly in Q.wiki under My Account > My Profile > Content API.

Authentication

The AI client authenticates via OAuth 2.0 – no tokens or credentials need to be entered manually. If your Q.wiki uses Entra ID SSO, the login process runs automatically. Each connection is automatically revoked after 30 days and must then be re-confirmed once.

During the OAuth dialog, you make two decisions:

Unit selection: You choose which unit's content the agent is allowed to search – only content from that unit will be returned, in line with how the standard Q.wiki search works.
Permission scope: Read-only access (agent can search and read content) or additionally write access (agent can post comments in Q.wiki).

Known limitations

Write access is limited to comments; creating page drafts will follow in a later version.
Available for Q.wiki NOW! only – not for on-premises installations.

Set up Q.wiki Assistant in Microsoft Copilot (coming soon!)