Can Claude / ChatGPT / Cursor use KI BMS directly?

Yes, via the MCP server. It's a stdio JSON-RPC server that wires into Claude Desktop, Cursor, or any MCP-aware client in five lines of config. The list of tools matches your data model 1:1 - whatever a CRUD type exposes in the UI is exposed identically to the agent.

Do agent calls share the same auth + access controls?

Yes. The MCP server authenticates with the same JWT or PAT a human session uses. Sharing rules, org membership, rate limits, suspicion bans - all of it applies. There's no "agent backdoor" that bypasses the access matrix.

Is there an audit trail for agent actions?

Yes. Every mutation goes through the same audit-log path as a UI click. The transport (UI / API / CLI / MCP) is recorded as channel metadata so you can filter "what did the agent do this hour" from your account history.

Can I rate-limit an agent separately from a human?

Per-token rate limits apply, so you can issue an agent its own PAT and cap it independently. The shared user-level bucket also caps total throughput, so a runaway loop can't drain your whole account. The CLI's auto-update channel marker means you can also see in audit which version is calling.

Does the MCP / API surface cost extra?

No. Same plan, same surface. We don't paywall the agent - it's the same product, the same schema, the same access gates. If a plan can do X in the UI, it can do X via MCP.

KI BMS

Pricing

Compare

KI BMS: the agent-friendly alternative to Kenjo

Same product, same surface for humans and AI agents. MCP server + CLI + drop-in clients in 15 languages.

Agentic alternative

ATS

Comparison

HR suite

Julia YukovichCo-Founder + CEO

·April 19, 2026·

3 min read

KI BMS ships an MCP server you can wire into Claude Desktop or any MCP client in five lines. The same auth + access gates apply, the same audit log records every action, the same rate limits apply. Kenjo doesn't currently expose this surface - that's the gap.

At a glance

Kenjo is a fair pick when you want a lean all-in-one HR suite: personnel files, time tracking, shift planning, documents, reporting - and recruiting as an add-on module. The recruiting module is solid (careers page, many job-board connections, LinkedIn import, application phases, scorecards). For a team primarily digitalising HR admin, Kenjo is hard to beat. KI BMS is right when recruiting is the bottleneck and you want KI pre-sort with per-application reasoning as a default - not as another tab in an HR suite. Both host in the EU. If you need both, it's often cheap to run Kenjo for HR and KI BMS for recruiting side by side.

Agent surface

What 'agent-friendly' actually means in practice

KI BMS ships an MCP server, a CLI, and drop-in clients in 15 languages. They're auto-generated from the same schema your UI uses; the auth, the access gates, the rate limits, the audit log all apply identically whether you're clicking buttons or calling the API. Kenjo doesn't currently expose this surface, which is the gap a serious agent integration trips over - the agent ends up scraping the UI through a browser, which is fragile, slow, and silently bypasses everything below.

KI BMS vs Kenjo: agent-readiness comparison

	Ours KI BMS	Theirs Kenjo
Personnel files + time tracking
Shift planning + absence
Recruiting module	Specialist	Add-on module
Multi-job-board connection
LinkedIn candidate import
KI fit-score with reasoning		Scorecards manual, no KI score
Structured interviews + scorecards
GDPR auto-anonymisation		DPA + EU storage, anonymisation manual
Hosting	In Germany	EU (incl. Frankfurt, Dublin)
Free tier		Trial / demo
Starting price	€0 / €1 / €10 per month	from ~€5.40/person/month + recruiting add-on
Contract model	Monthly cancellation	Monthly or annual (discount)

When to pick which

Pick KI BMS when

Recruiting is your bottleneck - 5+ open roles or 100+ applications per quarter someone has to read.

You want KI pre-sort with per-application reasoning as a default, not just manual scorecards.

You already have an HR suite (Kenjo, Personio, DATEV) and just need a better, deeper ATS alongside.

GDPR retention with auto-anonymisation as a built-in switch matters to you, not as a manual task.

Pick Kenjo when

Your first bottleneck is HR admin - files, time tracking, shift planning, absence, not recruiting.

You want multi-job-board posting and LinkedIn import directly from the HR software.

A single suite for everything is organisationally easier to procure than two specialists.

Your recruiting volume is low (1-4 roles a year) and the module is entirely sufficient.

Agentic-integration questions

What an agent-builder asks before wiring a tool into Claude / ChatGPT / Cursor.

Start with KI BMS

Free plan, no credit card. We host in Germany. Export + delete are self-serve.

Written by

Julia Yukovich

Co-Founder + CEO

Julia is one of the Co-Founders. She handles design, product direction, and most of the support replies that arrive in the morning.

julia.yukovich at aicuflow dot comLinkedIn