Kanbert · Copilot Studio

Can Kanbert time figures be asked of the assistant — without a new time-tracking product?

mcpsky is a hosted MCP platform: connect Kanbert, publish MCP endpoints, and let Copilot or Teams answer read-only billing and capacity questions.

30 minutes initial conversation · no obligation

01 — Diagnosis

The open decision

Whether time and billing figures in Kanbert can be asked of the assistant — in the Microsoft environment you already have, without write access to entries. Without a connection, managers export manually. The question is whether this layer is worth it for your case.

02 — Evidence

What ships today

Five read-only Kanbert tools: whoami, list efforts, effort summary, task efforts, and task search. Portal login, encrypted credential storage, hosted MCP URLs, Docker packaging, tests, and Copilot Studio connector import. Reporting only — no invented write API.

03 — Approach

Typical rollout

  1. 01
    Connect in the portal

    Add each Kanbert connection and test the API key before save.

  2. 02
    Publish an MCP endpoint

    Choose hosted MCP key or pass-through auth for your downstream client.

  3. 03
    Point Copilot at the URL

    Streamable HTTP MCP at /mcp/e/{endpoint-id} with your issued token.

06 — Next step

Talk it through

In 30 minutes you describe the starting point. We decide whether mcpsky fits your Microsoft and Kanbert setup — or whether the answer is no.