A payroll MCP server that answers “what was I paid?” and keeps pay changes behind their own tick

Two of the Ledgr actions are about the person asking: a pay summary and a list of payslips. That covers the everyday questions — what was my net pay last month, which months do I have payslips for — without a message to finance and without opening the tool.

The assistant has no view of its own. It works as the member who connected it, so an employee’s assistant has that employee’s view of pay, exactly as Ledgr shows it to them on the web, and nobody else’s.

Three actions are for the people who run payroll, and only appear for a role that already has those permissions in Ledgr:

• Read a member’s pay profile.
• Propose a salary revision, with the new amount, the date it applies from and the reason.
• Change a member’s salary directly.

Changing pay is never bundled with reading it. On the consent page it is its own tick, and it carries a warning in so many words: it lets the assistant change pay, and you should only tick it if you run payroll. A sensible way to start is to approve reading alone and use the proposal action, which puts a revision in front of a person, rather than the direct change.

Everything that makes a pay day happens in the tool, with a person at the screen: building the salary sheet from attendance, approving it, issuing payslips, and the claims, loans, final settlements and tax registers around it. None of those has an assistant action. An assistant can tell someone what they were paid; it cannot decide what anyone is paid this month.

That boundary is the catalogue itself, not a setting someone has to remember. There is no action to call, so there is nothing for a badly worded request to trigger.

Each action an assistant takes is listed in an activity log: which action ran, through which assistant, whether it was done, not allowed or failed, and when. A member sees their own log in Settings → Connected AI apps; an admin sees the organisation’s and can filter it by member. A request for something the member’s role does not allow shows up there as not allowed.

If finance would rather no assistant touched pay at all, there are three levers, and it is worth being plain about them. A member can leave the pay permissions unticked. A role without payroll permissions is never offered them. And an admin can switch AI assistants off for the whole organisation. There is no organisation setting that removes Ledgr alone.

Open Settings → Connected AI apps in Orbiz and copy your organisation’s address from there; the same screen has the steps for Claude, ChatGPT and Claude Code. When the assistant sends you to Orbiz to approve, tick reading for Ledgr and leave pay changes unticked unless you run payroll. The full picture of how connecting works is on the Orbiz MCP page.