Showcase is nice.
Getting paid is better.
Viboost captures your AI tool events and posts them to a public profile. Scribe captures your git commits, file changes, and Claude conversations — then turns them into invoices. Your work stays on your machine.
Side by side
Same idea, very different goals.
| Feature | Scribe | Viboost |
|---|---|---|
| What it captures | Git commits, file changes, Claude Code conversations | MCP tool events (write_file, terminal_cmd) during AI sessions |
| Retroactive history | Git history going back years — no session required | Only captures activity while MCP is connected |
| Works without AI tools | Yes — tracks git and files regardless of what editor you use | No — requires an active MCP-connected AI session |
| Invoicing | Generate invoices directly from your tracked timeline | |
| Where your data lives | Local SQLite on your machine | Viboost cloud servers |
| Visibility | Private by default, optional team sync | Public profile — the whole point is sharing it |
| Claude Code tracking | Parses conversation logs from ~/.claude/projects/ | Captures tool calls via MCP server |
| Setup | Download app, point at your code folders | Add MCP server config entry, get API key |
| Works across all editors | Yes — tracks git, not your editor | Only editors that support MCP (Cursor, Windsurf, Claude) |
| Pricing | Free / $12/mo Pro | Free tier available, paid plans for teams |
Which tool fits?
Stick with Viboost if you
- Want a public profile to showcase your AI-assisted work
- Build in public and want others to see your activity feed
- Care more about visibility than billing or privacy
- Only work with MCP-enabled AI tools (Cursor, Windsurf, Claude)
Switch to Scribe if you
- Bill clients and need invoices backed by tracked work evidence
- Want your activity data private, not posted to a public profile
- Need retroactive history — git commits from months or years ago
- Use editors or workflows outside of MCP-connected AI tools
- Use Claude Code and want full conversation-level tracking
Common questions
How is Scribe different from Viboost?
Viboost is built for building in public — it listens to your MCP tool events and displays them on a public developer profile. Scribe is built for getting paid: it reads your git history, file system, and Claude Code conversations to create a private timeline you can turn into invoices. Viboost sends your data to their cloud; Scribe stores everything locally.
Can Scribe capture historical work like Viboost can't?
Yes. Scribe reads your git history retroactively, so it can surface commits from months or years ago — not just what happened during today's AI session. If you have 3 years of commits across 20 repos, Scribe can pull all of it in. Viboost only captures events that pass through its MCP server in real time.
Does Scribe work if I'm not using AI coding tools?
Yes. Scribe tracks git commits and file changes regardless of which editor or workflow you use. Viboost requires an active MCP-connected session in Cursor, Windsurf, or Claude to capture anything.
Is my data private with Scribe?
Everything is stored in a local SQLite database on your machine. No code, file content, or activity data leaves your machine unless you explicitly sync to a team hub. Viboost by design posts your activity to a public profile on their servers.
Can I use both Scribe and Viboost?
Sure — they serve different purposes. Viboost for your public developer profile; Scribe for invoicing and private work records. They don't conflict.
Scribe is in private beta
We're rolling out access gradually. Join the waitlist and we'll notify you when your seat opens.
Get more like this
Developer insights and product updates.