Can Claude / ChatGPT / Cursor use Contact Book 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.

Contact Book

Compare

Contact Book: the agent-friendly alternative to UpHabit

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

Agentic alternative

Personal CRM

Keep in touch

Comparison

Julia YukovichCo-Founder + CEO

·January 9, 2026·

3 min read

Contact Book 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. UpHabit doesn't currently expose this surface - that's the gap.

At a glance

UpHabit's pitch is import everything and let reminders do the rest: it syncs your phone contacts, lets you tag and group them, and nudges you on a schedule. Contact Book takes the opposite starting point - a smaller circle you add on purpose, with a sentence of context per person, hosted in Germany with no trackers. Pick UpHabit if you want your whole address book pulled in and reminded against; pick us if you'd rather keep a thin, curated, private log of the relationships that genuinely matter.

Agent surface

What 'agent-friendly' actually means in practice

Contact Book 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. UpHabit 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.

Contact Book vs UpHabit: agent-readiness comparison

	Ours Contact Book	Theirs UpHabit
Auto-import phone contacts	Manual / file import
Per-person cadence reminders
Conversation log
Life events + gifts		Limited
Family / relationship graph
Curated-circle by default		Whole address book
Hosted in Germany
No third-party trackers		Unclear
Free tier

When to pick which

Pick Contact Book when

You'd rather curate a small circle than have your whole address book imported.

You want context per person - the log, the life events, the family graph - not just reminders.

Hosting in Germany and a no-tracking posture matter to you.

Pick UpHabit when

You want your entire phone address book pulled in and reminded against in one move.

Reminders are the whole job for you and you don't need a deep per-person record.

Agentic-integration questions

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

Start with Contact Book

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