Join the list →
OPTIONAL AI working HR underneath

Ask who's away. Keep the reason private.

Give an approved assistant an organisation-bound route to practical HollyHR data. Core HR still does the work; the developer-preview connection is optional.

Join the early-access list Read the connector guide

Controlled early access · MCP is a developer preview · public connector galleries are not launched

Organisation set by the key Selected higher-risk fields withheld Core HR works without AI
Two shipped read tools provide bounded fields; the approved assistant composes the answer.
AI-ready, in plain English

A controlled connection, not another HR chatbot.

AI-ready HR software should answer a useful question without handing over the whole filing cabinet. HollyHR exposes bounded operations through MCP and its API.

You supply the assistant. HollyHR fixes the organisation from the key and records each request separately from the human-action audit trail.

Inspect the MCP contract
The key fixes the organisation. Request records capture route, outcome and row count — not prompts or returned payloads.
Start with an ordinary job

Three questions worth making easier.

01

Who is away this week?

Read approved dates and status without a detailed absence reason.

02

How much leave is left?

Use the current balance when the key has the right scope.

03

What work context is recorded?

Find approved details such as role, manager and organisation structure.

Smaller on purpose

The assistant gets a projection, not a copy of the HR record.

Each MCP operation starts from an approved field list. Selected values are then withheld, redacted or bucketed.

  • Names, work context, dates and balances can be returned when in scope.
  • Home, bank, tax, compensation and document-file fields are withheld.
  • Detailed absence categories are reduced to a broad bucket.
An approved assistant can combine the separate people and time-off results; HollyHR does not return this as one joined record.
Human control, before the commit

An assistant can prepare a change. It cannot quietly improvise one.

HollyHR validates and freezes a proposed write. The host presents it for confirmation; only that signed, short-lived payload can be committed.

This developer preview is not generally enabled. Standard, separate approval, the right scopes, environment enablement and host confirmation must all be present.

Developer-preview contract. Writes are not generally enabled and are attributed to the API key, not a named host user.
Open platform, correctly packaged

Use an assistant when it helps. Use the API when code is clearer.

API and MCP reads are on every plan. Signed webhooks and approved writes have a different boundary.

API and MCP reads are on Free; signed webhooks are Standard; writes need Standard and separate approval.
The important boundary

Useful access without pretending the hard decisions disappeared.

A controlled connection can reduce lookup work. People decisions, privacy and provider due diligence remain human responsibilities.

The current contract

What a buyer can rely on.

  • Core workflows stay in the normal HollyHR product.
  • A System Admin creates a revocable, organisation-wide scoped key; it does not inherit the connecting user's role.
  • HollyHR supplies the connection, not the assistant. The host has its own data terms.
Not claimed

Where the product deliberately stops.

  • No autonomous HR, legal or employment decisions.
  • Names, work context, dates and balances can still be returned when approved.
  • No public connector-gallery listing, delegated-user OAuth or named-user write attribution yet.
AI and HR software questions

Clear answers before you connect anything.

Availability, data access, human control, compliance and cost in plain English.

Does HollyHR use AI to run HR?

No. Core HR works without AI. The API and developer-preview MCP are optional routes for an approved tool to access selected data.

Can Claude, ChatGPT or another assistant connect to HollyHR?

HollyHR hosts a developer-preview MCP endpoint using an organisation-scoped API key, not each user's role. Public connector galleries are not launched, so setup depends on the host.

What can an assistant read from HollyHR?

Current MCP tools cover approved people, time-off and reference data. Projections withhold selected home, bank, tax, compensation and document-file fields and bucket absence categories. Names, work details, dates and balances remain visible when in scope.

Can an assistant change an HR record?

Writes require Standard, separate HollyHR approval, write and mcp:write scopes, environment enablement and host confirmation. Write mode is off by default and not generally enabled.

Is connecting an AI assistant automatically UK GDPR compliant?

No. HollyHR supplies scoping, projections, revocable keys and request records. Your organisation must assess purpose, lawful basis, access and the host's retention, training, region and sub-processors; a DPIA may be appropriate.

What does AI and developer access cost?

REST API and MCP reads are on every plan, including Free. Signed webhooks are Standard. Programmatic writes need Standard plus separate approval. The external provider sets its own charges.

Bring us one practical HR question.

Join the early-access list. If the controlled connection matters, tell us the question and assistant you use.

Join the early-access list Read the connector guide

Joining records interest; it creates no account or AI connection