Deploy the Q.wiki Assistant via MCP in Microsoft Copilot (new Copilot Studio experience)

Built, published and rolled out to your whole organization in about 30 minutes.

How it works:  You create an agent in Microsoft Copilot Studio, add our instructions and best-practice skills, connect it to your Q.wiki via the MCP interface – and make it available to all users in Microsoft 365 Copilot and Microsoft Teams. Background and special cases: see the  FAQ  .

The screenshots in this article show the German interface – the steps below use the English labels.

What you need

Part 1: Create and publish the agent

 1  Open the new Copilot Studio experience

1. Open  copilotstudio.microsoft.com  and sign in with your work account.
2. Enable the  “New experience”  toggle in the top-right corner – or click  “Try now”  in the banner.

 2  Create a new agent

1. Click  “New agent”  and, under  “Optimize business processes”  , choose the option  “Agent”  (labeled “Uses Copilot Credits”) –  not  “Create with standard orchestration” (the classic agent type).
2. Name it  Q.wiki Assistant  .

 3  Set the icon and instructions

The agent opens in the  “Build”  tab:

1. Use the pencil icon (①) to set the  icon  – e.g. the bundled Ariadne logo from the attachments (  10-ariadne-logo.png  ) or your own logo (PNG, max. 100 KB).
2. Paste our proven instructions into the  “Instructions”  field (②) and save with  “Save”  :

You are the Q.wiki assistant for a connected Q.wiki management system. You answer questions about that management system and you run the skills attached to you.

Everything you say about the management system must come from Q.wiki, retrieved in this conversation with the Q.wiki tools. Never state content from your own knowledge and never invent a page, a title, a URL, a date or a responsible person. If you find nothing, say so instead of filling the gap. For requests that have nothing to do with this organisation, say in one sentence that you only cover Q.wiki content.

Never create or change anything in Q.wiki — no comments, no pages, no attachments — before the user has seen the exact text and confirmed it. This holds even when a skill offers to write on its own.

Be direct and concrete, like a competent colleague. Answer in the language the user writes in; if that is unclear, answer in German, and use "Du" unless the user writes "Sie".

For a question about the management system that no other skill covers, use `qwiki-frage-beantworten`.

 4  Choose the model

In the  “Model”  section (③), pick a model and save. We recommend  Claude Sonnet 5  – it is not mandatory, other models work as well (  details in the FAQ  ).

 5  Connect Q.wiki via MCP

1. In the  “Tools”  section (⑤) click  +  , then in the dialog select  “Add”  >  “Model Context Protocol (MCP)”  and fill in the fields:

2. Confirm with  “Add”  and create the connection (  “Create new connection”  ): sign in with your Q.wiki account in the pop-up, choose the  unit  (your main unit if in doubt) –  read access  is sufficient.
3. The Q.wiki tools (full-text search, page retrieval, roles, and more) appear in the list – save with  “Save”  .

 6  Upload the best-practice skills

In the  “Skills”  section (④) click  +  >  “Upload a skill”  and upload the skill ZIP files from the attachments one by one, unchanged (do not unzip). The agent activates matching skills automatically – what each skill does: see the  FAQ  .

 7  Test

1. In the  “Preview”  tab, ask a real question from your day-to-day work, e.g.  “How does our complaint handling process work?” 
2. Check in the  “Activity trace”  that  Qwiki MCP  is being called, and spot-check the source links at the end of the answer.
3. Optional: use the  “Evaluate”  tab for structured, repeatable test sets.

 8  Publish and submit for approval

1. Click  “Publish”  in the top-right corner and enable the  “Teams + Microsoft 365”  channel in the dialog (①).
2. Under “Turn on Microsoft 365”, tick  “Make agent available in Microsoft 365 Copilot”  (③). Via “Edit details” you can add the store description, e.g.  “Answers questions about our management system – straight from Q.wiki, always with source links.” 
3. Confirm with  “Publish”  (④) – this can take a few minutes; it is not possible on a trial license.
4. Then open  “Availability options”  (②) in the “Agent preview” >  “Show to everyone in my org”  >  “Submit for admin approval”  (may also read “Submit to org catalog”). Status: “Waiting for approval”.
5. Let your Microsoft admin know – ideally with a link to  part 2  .

Part 2: Approve and roll out (Microsoft admin)

From here your Microsoft admin takes over (  Global Administrator  role) – this part works on its own.

 9  Approve and deploy the agent

1. Open  admin.microsoft.com  >  Agents > All agents > “Requests”  and select the  Q.wiki Assistant  (“Pending review”); under “Data & tools” you can see the Q.wiki MCP connection.
2. Run  “Publish to store”  : audience (all or specific users/groups),  pre-installation  (recommended – otherwise users add the agent themselves from the store), policy template (the default is fine), review the permissions and grant  “admin consent”  .
3. Finish with  “Publish”  – the agent appears in the store under  “Built by your org”  .

 10  Pin the agent (optional, recommended)

Under Agents > All agents, click the published Q.wiki Assistant – in the detail pane that opens you can pin it for all users directly in the left-hand Copilot navigation.

Note: The agent may appear twice in the list. Only one of the two entries can be pinned – use the one that offers the option

What it looks like for your users

The Q.wiki Assistant appears in  Microsoft 365 Copilot  and Microsoft Teams in the sidebar under  “Agents”  – pinned, or via  “All agents”  in the “Built by your org” section. The first time, users click  “Connect”  or “Sign in”, log in with their  own Q.wiki account  and simply resend their question.

Licenses & costs

 Does the agent consume credits even with a Microsoft 365 Copilot license? Yes, always.  The new agents are billed on a usage basis via  Copilot Credits  (1 credit = 0.01 USD pay-as-you-go) – unlike classic agents, they are not covered by the Copilot license. The license is still useful: among other things, it covers the maker’s Copilot Studio access. Microsoft is moving this agent type to usage-based billing across the board – including previously created agents.

•  What is billed:  building via chat, testing (Preview/Evaluate) and every use. Manual configuration (Build/Monitor) is free. Without credits, the agent stops (“You need credits to continue”).
•  What does a request cost?  Microsoft bills by effort, not per question: simple questions consume only a few credits (a matter of cents), elaborate multi-step tasks accordingly more. You will see the real consumption after the first few days in the Power Platform admin center – details in the Copilot Credits Guide in the attachments.
•  Staying in control:  allocate credits per environment and set  monthly limits per agent  (Power Platform admin center); spending policies and reports in the Microsoft 365 admin center under “Copilot” > “Cost management”.

Details:  Microsoft Copilot Credits Guide (PDF, August 2026)  in the attachments and  Microsoft Learn: Usage-based billing  .

FAQ

Troubleshooting

Related articles & links

•  Q.wiki MCP server – overview & endpoint 
•  MCP interface: use Q.wiki knowledge with ChatGPT, Copilot & co.