Setting MetronHR up in Microsoft Copilot

Microsoft 365 Copilot reaches MetronHR through an agent: in Copilot Studio create a tool of type Model Context Protocol, enter app.metronhr.de/mcp as the address, choose OAuth 2.0 with Dynamic discovery and publish the agent to the Microsoft 365 Copilot channel. GitHub Copilot in VS Code only needs the mcp.json.

As of:15. September 2026

Which Copilot is meant

The name carries two products, and the route to the same server differs in each. The address, the rights and the business's release, on the other hand, are identical.

  • Microsoft 365 Copilot

    Where the address goes
    Copilot Studio, a tool of type Model Context Protocol on an agent. The agent is then published to the channel.
    Who sets it up
    Whoever may build agents in the tenant.

  • GitHub Copilot in VS Code

    Where the address goes
    The workspace's .vscode/mcp.json file.
    Who sets it up
    Each person on their own machine.

As of 15. September 2026. Both speak the Streamable HTTP transport; SSE is no longer served by either side.

Microsoft 365 Copilot: the agent in Copilot Studio

Microsoft calls the procedure the MCP onboarding assistant. The server's description is not decoration: the agent's orchestrator uses it to decide whether to call MetronHR at all.

  1. 1. Release it for the business first

    In MetronHR under company settings, Integrations section: switch AI connections on, name the roles, decide about writing separately. Without that step the sign-in later ends with a refusal.

  2. 2. Create the tool

    In Copilot Studio on the agent's Tools page: Add a tool, New tool, Model Context Protocol. Enterhttps://app.metronhr.de/mcp as the Server URL, plus a name and a clear description of what the server can do.

  3. 3. OAuth 2.0, the Dynamic discovery variant

    MetronHR handles dynamic client registration including discovery, so the client ID, the secret and the authorisation and token addresses stay empty. Choose Create, then create a new connection and attach the tool to the agent with Add to agent.

  4. 4. Publish the agent

    An agent for Microsoft 365 Copilot is not rolled out by itself. After publishing it the first time, connect the Teams and Microsoft 365 Copilot channels; after that it can be addressed in the chat.

The field names are written here the way Microsoft writes them, even where the interface is in German: they are English in the Microsoft Learn documentation, and a translation of our own would get in the way when searching.

GitHub Copilot in VS Code

One file in the workspace, nothing else. VS Code asks for authorisation on the first call and runs the same browser sign-in flow as any other client.

.vscode/mcp.json

{
  "servers": {
    "metronhr": {
      "type": "http",
      "url": "https://app.metronhr.de/mcp"
    }
  }
}

Which tools are available afterwards is decided by the consent dialog, and that in turn by the rights of the person signed in. The full list is on the page about the MCP server.

What is left to sort out on the Microsoft side

Three points do not depend on MetronHR. Knowing them beforehand saves hunting for a fault that is not one.

  • Rights in the tenant

    What to do
    Building and publishing agents in Copilot Studio is a permission of its own. It sits with the Microsoft administration.

  • Data policies

    What to do
    Access to MCP servers runs through Power Platform connectors. A policy on those governs this agent too.

  • Distribution

    What to do
    A published agent is at first available only to the person who published it. For the whole business it belongs in the organisation's catalogue.

As of 15. September 2026. This is based on the Microsoft Learn guides to connecting an existing MCP server and to publishing agents. Whatever Microsoft changes there changes here too.

Questions about Microsoft Copilot and MetronHR

What we are asked most often about it.

No. An external MCP server does not hang directly off the chat, it hangs off an agent. The agent is built in Copilot Studio, gets the server there as a tool and is then published to the Microsoft 365 Copilot channel. After that it is available in Copilot and in Teams.

OAuth 2.0 with the Dynamic discovery variant. MetronHR handles dynamic client registration including discovery, so the client ID, the secret and every address field stay empty. The Dynamic and Manual variants demand values that do not exist here.

Streamable HTTP, on both sides. Since August 2025 Copilot Studio supports only this transport, and MetronHR speaks it: a JSON-RPC request as a POST to app.metronhr.de/mcp, with no session.

That route is shorter: put the address in the workspace's .vscode/mcp.json, type http. VS Code asks for authorisation on the first call and runs the same browser sign-in flow as any other client.

Yes. AI connections are off out of the box for the business, the list of roles decides who may connect, and writing is a third, separate release. An agent in Copilot Studio is no exception.

Yes. Access to MCP servers in Copilot Studio runs through Power Platform connectors. A policy governing those connectors therefore also governs the agent's access to MetronHR. That is a setting on the Microsoft side, not in MetronHR.

Question not answered here? Every step is explained in the help centre.

Bring your hours to where the work already happens

One agent in Copilot Studio, one address, and the release stays with the business.

See the prices

No credit card, cancel any time

Related

Where to go from here, and what waits for you there.