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 Onlyfy by XING

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

Agentic alternative

ATS

Comparison

DACH

Finn GlasCo-Founder + Engineering

·January 19, 2026·

2 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. Onlyfy by XING doesn't currently expose this surface - that's the gap.

At a glance

Onlyfy by XING is right when your recruiting focus is active sourcing - in-house recruiters direct-messaging XING profiles, with a 21M DACH-profile talent pool in the same tool. KI BMS is right when your recruiting focus is inbound - public roles, incoming applications, KI pre-sorting, fast rejection templates. Both EU-hosted; both GDPR-clean.

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. Onlyfy by XING 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 Onlyfy by XING: agent-readiness comparison

	Ours KI BMS	Theirs Onlyfy by XING
Network-sourced talent pool		21M XING profiles
Direct messaging (sourcing)
Careers page included
Multi-job-board posting
KI fit-score built in		Add-on
Hosted in Germany
GDPR auto-anonymisation		Configurable
Free tier
Starting price	€0 / €1 / €10 / month	Quote (higher)
Contract model	Monthly	Annual + sourcing licences

When to pick which

Pick KI BMS when

Your hires come primarily from public roles + careers page + referral.

Active sourcing isn't your main channel - application volume is sufficient.

KI pre-sort with per-application reasoning > talent-pool size.

Pick Onlyfy by XING when

Senior and specialist roles where public applications barely come in and active sourcing is the only path.

You have in-house sourcing recruiters who message XING profiles daily.

DACH focus; XING is the standard platform in your market.

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

Finn Glas

Co-Founder + Engineering

Finn is one of the Co-Founders. He owns the engineering side, the infrastructure, and most of the late-night fixes that ship before anyone notices.

finn.glas at aicuflow dot comLinkedIn Website