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 Camera roll

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

Agentic alternative

Comparison

Photos

Finn GlasCo-Founder + Engineering

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

At a glance

Photos of starters at peak are the most accurate journal you already keep - they're just not labelled and not searchable. Sourdough Tracker doesn't replace your camera; it just gives each photo a home next to the entry it belongs to. Six months in, your camera roll has 200 photos of jars and you can't tell which feed each one was; the journal has 200 photos attached to feeds, with rise % and ambient temp next to each.

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

	Ours Sourdough Tracker	Theirs Camera roll
Photos in chronological order
Labelled with rise %, hydration
Filterable by starter
Compare two bakes side-by-side		DIY
Survives a phone replacement		If you sync

When to pick which

Pick Sourdough Tracker when

You want to look at last September's bake to compare to today's.

Pick Camera roll when

You bake once and snap one photo - any tool works.

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