Can Claude / ChatGPT / Cursor use Sourdough Tracker 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.

Sourdough Tracker

Compare

Sourdough Tracker: the agent-friendly alternative to A paper notebook

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

Agentic alternative

Comparison

Notebook

Finn GlasCo-Founder + Engineering

·January 8, 2026·

1 min read

Sourdough Tracker 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. A paper notebook doesn't currently expose this surface - that's the gap.

At a glance

Paper has a real advantage: nothing more honest than a flour-dusted page that's been near the dough. It also has a real disadvantage: you can't search it, you can't sort it, you can't filter feeds vs bakes, and the photos live in a separate device. Sourdough Tracker is the digital equivalent that respects what paper does well - one-tap entries, no nag, your data stays yours - while adding what paper can't: search, filtering, photos in line with the entry they belong to, and per-starter sharing. Many bakers happily run both.

Agent surface

What 'agent-friendly' actually means in practice

Sourdough Tracker 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. A paper notebook 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.

Sourdough Tracker vs A paper notebook: agent-readiness comparison

	Ours Sourdough Tracker	Theirs A paper notebook
Tactile + flour-friendly
Searchable across entries
Photos inline with entries
Sortable feed vs bake feed
Survives a coffee spill		Maybe
Share one starter w/ a friend
Battery / wifi required	Yes

When to pick which

Pick Sourdough Tracker when

You bake more than once a month and want patterns to emerge.

Photos matter to you - and you want them on the same page as the entry.

You want a friend (or your kitchen co-baker) to see one starter without the rest.

Pick A paper notebook when

You want zero screens at the kitchen counter, period.

You bake once or twice a year as a hobby and don't need search.

Agentic-integration questions

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

Start with Sourdough Tracker

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