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 Ashby

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

Agentic alternative

ATS

Comparison

Premium

Finn GlasCo-Founder + Engineering

·January 18, 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. Ashby doesn't currently expose this surface - that's the gap.

At a glance

Ashby is right when you're a 100+-staff tech company with dedicated TA and want an all-in-one stack: ATS + CRM + analytics + scheduler + sourcing in one tool. KI BMS is right when you're 8-100 staff and want a dedicated ATS productive in 10 minutes. Ashby is deep, powerful, expensive; KI BMS is lean, fast, transparent on price. Pipeline functions overlap; the surroundings differ.

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

	Ours KI BMS	Theirs Ashby
Hosted in Germany
Careers page included
Analytics suite	Standard	Best-in-class
Talent CRM	Talent pool	Full CRM with nurture
Scheduler built in
KI fit-score built in		Add-on (Ashby AI)
Multi-voice scorecards
Free tier
Starting price	€0 / €1 / €10 / month	Quote (4-5-figure per year)
GDPR auto-anonymisation		Configurable
Language	DE + EN	EN-first

When to pick which

Pick KI BMS when

You're 8-100 staff in DACH. Ashby's depth isn't needed, the price hurts.

Hosting in Germany + DPA in 24h are mandatory.

Public pricing + monthly contracts.

Pick Ashby when

You're 100+-staff tech with ambitious analytics needs (funnel cohorts, pass-through rates, diversity reporting).

Your TA has 3+ dedicated sourcers + a coordinator team for scheduling.

You have procurement with multi-year contracts and accept a 5-figure annual budget.

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