Setting MetronHR up in Claude Desktop and Claude Code

In Claude Desktop enter the address app.metronhr.de/mcp as a custom connector, and in Claude Code put the same entry in the configuration. Both then open the sign-in flow in the browser. There is no secret; the client registers itself.

As of:15. September 2026

Claude Desktop

Settings, Connectors section, add a custom connector, enter the address. Claude Desktop then opens the sign-in in the browser; anyone not yet signed in to MetronHR signs in there and then sees the consent dialog with the rights in plain words.

The address that belongs there

https://app.metronhr.de/mcp

Claude Code

The same entry as a file. Then authorise the connection in the program; the same browser flow as above follows.

The workspace configuration

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

What you can do with it

Alongside the tools, the server provides2 ready-made reports and three reference lists: tenant, departments and services. The assistant therefore does not have to guess the shape of the business.

  • Check the month end

    Where the answer comes from
    A ready-made report over a period's time entries and absences, optionally for one person.

  • Overtime by department

    Where the answer comes from
    The second ready-made report. It calculates against the stored working time model, not against an assumption.

  • Build an integration of your own

    Where the answer comes from
    Claude Code reads along through the same tools while the code is being written. The binding form is in the app's OpenAPI document.

As of 15. September 2026. Which tools appear is decided by the rights of the person signed in and by the business's release.

The full list of tools, the protocol revision and the server's limits are set out on the page about the MCP server.

Questions about Claude and MetronHR

What we are asked most often about it.

One that knows custom connectors. The address goes into the settings under Connectors, and Claude does the rest itself: registration with the authorisation server and sign-in in the browser.

Only where the address goes. Claude Desktop takes it in the settings dialog, Claude Code in a configuration file. After that both run the same sign-in flow in the browser, and both get the same tools.

No. The rights hang on the person connecting and on the business's release, not on the client. A tool without a right does not even appear in the list the assistant receives.

Only with the business's writing release and only for the roles listed there. The call then takes the same route as an entry in the product: lock periods, collision checks and rights on the client apply unchanged.

The server runs at our end in Germany, and the client talks to it directly. What Claude makes of the answers is processed by Anthropic; that decision comes before the connection and belongs in the contract with that provider.

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

Analyse your hours where you already work

One address, one sign-in flow, 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.