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 Lead-Table

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

Agentic alternative

ATS

KI recruiting

Comparison

Finn GlasCo-Founder + Engineering

·February 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. Lead-Table doesn't currently expose this surface - that's the gap.

At a glance

Lead-Table and KI BMS target the same audience: German HR teams that want modern, KI-assisted recruiting. Lead-Table leans into active sourcing and pipeline visualisation. KI BMS is broader: careers page + public application form included, KI fit-score with reasoning as a default, GDPR retention windows built in, public clear pricing. If your recruiting is mostly inbound (public role -> application arrives), KI BMS is the more natural fit. If it's mostly outbound (you source actively), look at both.

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. Lead-Table 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 Lead-Table: agent-readiness comparison

	Ours KI BMS	Theirs Lead-Table
API + webhooks + MCP		API yes
KI fit-score with reasoning
Kanban pipeline
Active sourcing tools	Talent pool
Careers page included		Limited
Public application form
Auto-mails on stage change
Per-candidate GDPR retention
Public pricing
Free tier
Hosting region	Germany	Germany

When to pick which

Pick KI BMS when

Recruiting is mostly inbound: you publish a role and applications arrive via the careers page + LinkedIn.

You want to see prices publicly before signing up.

Per-candidate retention + auto-anonymisation should be a built-in default.

A public free tier you can try without contact is important to you.

Pick Lead-Table when

Active sourcing is the main channel: you live in LinkedIn and need tools that pull profiles into the ATS.

You've planned a sales cycle with the vendor and value hands-on onboarding.

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