Yes. Krokul CRM integrates with Microsoft Copilot through its MCP server at https://app.krokul.com/mcp. You add the server to an agent in Copilot Studio, and the agent uses Krokul tools for deals, contacts, tasks and reports. Published to Teams and Microsoft 365 Copilot, the agent asks each colleague to sign in to Krokul and acts with that person's role.
A finance colleague asks the Krokul agent in Teams which clients are overdue this month. Copilot calls the Krokul tool client_company_read_debtors with that person's sign-in and lists the overdue invoices by client company. A sales manager asks next. With the agent role in Krokul, that answer covers only the manager's own clients.
Right after a client meeting, you tell the agent in Microsoft 365 Copilot what was agreed. The agent finds the deal with card_read_list, saves the summary as a comment with activity_create and books the follow-up with task_create for the date you named. The comment appears in the deal feed.
The tools report_conversion and report_stage_duration return conversion between stages and the average days a deal spends in each. Copilot compares them with last month and drafts three talking points for the sales meeting. The figures come from the Krokul server.
You ask the agent to move every stalled deal of a departed manager to a colleague. Each Krokul write tool accepts the flag dryRun, so Copilot first shows the request card_bulk_update would send. Nothing changes until you confirm.
| Microsoft Copilot | Direction | Krokul | When |
|---|---|---|---|
Agent tool call for reading (card_read_list, contact_find, client_company_read_debtors) | Krokul → Copilot | Deals, contacts, debtors | A user asks about Krokul data |
Agent tool call for writing (task_create, activity_create, card_update_status) | Copilot → Krokul | Tasks, comments, deal stages | A user asks the agent to record something |
Agent tool call for reports (report_dso, report_conversion, report_stage_duration) | Krokul → Copilot | Reports calculated by Krokul | A user asks for analysis |
| MCP resources (modules, connectors, custom field types) | Krokul → Copilot | Krokul registry of the company | The agent needs context about the setup |
| OAuth 2.0 sign-in of each user (Dynamic discovery) | Copilot → Krokul | Krokul user, company and approved permissions | First use of the agent, then token refresh |
https://app.krokul.com/mcp as the Server URL.https://app.krokul.com/mcp then serves the key holder.Yes. Add https://app.krokul.com/mcp to a Copilot Studio agent as a Model Context Protocol tool with OAuth 2.0, and the agent uses Krokul tools inside Teams and Microsoft 365 Copilot.
No. With OAuth each person signs in to Krokul separately, and Krokul checks that person's role on every call. An agent role sees its own deals only.
No. Remove, merge, cancel, archive and refund tools are not offered over MCP. The agent creates and updates records within the permissions you approved.
Yes. Copilot Studio reads the tool list from the MCP server, and tools added or removed in Krokul appear or disappear in the agent without a new setup.
Copilot Studio uses MCP with generative orchestration turned on, and your Power Platform data policies govern the MCP connection like any other connector. Remove, merge, cancel, archive and refund stay with people in the Krokul interface. One connection covers one Krokul company.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Microsoft, Microsoft Copilot, Copilot Studio and Microsoft Teams are trademarks of Microsoft Corporation. Krokul is not affiliated with Microsoft.