AI & MCP · Included on every plan

Run payroll in plain language.

Force HRM is the first payroll in Kenya you can operate through Claude — and any assistant that speaks the Model Context Protocol. Ask questions, run summaries, log leave, and prepare payroll from a conversation.

The Model Context Protocol (MCP) is the open standard that lets AI assistants securely use real software. Force HRM ships an MCP server with 90+ payroll and HR tools — so your assistant doesn't just answer questions about payroll, it operates yours, with your permissions.

Claude Claude Desktop Claude Code Cursor Any MCP client

Connect Claude in three steps.

No API keys to copy, nothing to install. Force HRM speaks OAuth 2.1 — Claude discovers everything from one URL.

01

Open Connectors in Claude

In Claude (web or desktop), go to Settings → Connectors → Add custom connector.

02

Paste the Force HRM server URL

That is the only thing Claude needs — it discovers the sign-in flow on its own.

03

Sign in and approve

Log in with your Force HRM account, approve access, and pick which company to work in. Your assistant now has your payroll — with your permissions, nothing more.

Claude · Settings · Connectors

Remote MCP server URL

https://mcp.forcehrm.com/hrm-connect

OAuth 2.1 with PKCE — no keys to manage

Scoped to your account and chosen company

Revoke access anytime from Force HRM

Not using Claude? Still works.

Any MCP-capable client can connect over HTTP. OAuth clients sign in like Claude does; everything else uses a personal access token.

Claude Code

terminal

One command in your terminal — Claude Code walks you through the same sign-in Claude uses.

claude mcp add --transport http force-hrm https://mcp.forcehrm.com/hrm-connect

Other MCP clients

mcp.json

Generate a personal access token at forcehrm.com/mcp/auth, then point your client at the server:

{
  "mcpServers": {
    "force-hrm": {
      "url": "https://mcp.forcehrm.com/hrm-connect",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Then just ask.

Every prompt below maps to a real tool on the server — these aren't mockups.

"Give me a payroll summary for this month."

Gross, deductions, and net across the company — totals and per-employee.

"Whose contracts expire in the next 60 days?"

Contract expiry alerts, with renewal straight from the chat.

"Log 3 days of sick leave for Amina from Monday."

Leave recorded against her balance and reflected in the next run.

"Generate July payroll and show me what changed."

Draft payroll computed; you still review and approve in the app.

"Are we ready to pay everyone? Anything missing?"

Payment readiness check — flags missing bank details before payday.

"Send everyone their payslips."

Payslips delivered to the employee app, on your instruction.

First thing your assistant does after connecting: ask which of your companies to work in. Every action after that is scoped to it.

Your data, your permissions.

OAuth 2.1 + PKCE

The modern authorization standard — Claude never sees your password, and there are no long-lived API keys to leak.

Your permissions exactly

The assistant can only see and do what your own Force HRM account can. Nothing is elevated.

Company-scoped

Every session works inside one selected company; switching is explicit, never implied.

Revocable + rate-limited

Cut access anytime from your account. Every token is throttled server-side.

On every plan. No add-on, no upsell.

Start a trial, connect Claude, and ask your payroll something.

Start free trial
WhatsApp Start free trial