SecondBrain
Ask the Brain
Index/Sourceupdated Sat May 09 2026 08:00:00 GMT+0800 (Philippine Standard Time)

Printing Press (Nate Herk video)

printing-pressclimcpclaude-codeagentstooling

Printing Press (Nate Herk video)

"Printing Press Just 10x'd Everyone's Claude Code" By Nate Herk (AI Automation) · YouTube, 2026

A walkthrough of Printing Press — a tool that gives Claude Code (and other agents) a library of pre-built CLIs plus a "factory" for turning any tool into one. Pitched as a more token-efficient alternative to MCP servers for agent ↔ tool integration. See CLI vs API vs MCP for the full comparison.

Key claims

  • CLIs beat MCPs and APIs for agents because they're token-efficient, agent-native, and produce short pre-formatted output. Cited benchmark: MCP used 35× more tokens than the CLI on the same task; reliability dropped from 100% (CLI) to 72% (MCP) as tasks got harder.
  • MCPs leak tokens passively. Even when not invoked, every loaded MCP server adds tool descriptions to the agent's context on every turn. /context in Claude Code reveals the bloat.
  • CLIs let you wrap sites with no public API. Demos: School (community platform), Craigslist, ESPN, Domino's, AllRecipes (with anti-scrape). Printing Press reverse-engineers them via real Chrome sessions.
  • The "School" example: 132,000 tokens of API response → only ~2,000 tokens hit the Claude context window (the CLI digested and summarized before returning). This is the core efficiency story.
  • Built by Mike Van Horn, with the CLI-as-better-than-official-CLI idea credited to Peter Steinberger (creator of OpenClaw, who built gog to replace Google's official gws CLI).
  • Tool hierarchy for agents (Nate's tier list): CLI > API > MCP. Default to CLI; if there's an API but no CLI, build one with Printing Press; only fall back to MCP when there's nothing else.

Concrete tools shown

  • pp-school, pp-tally, pp-youtube — Nate's custom CLIs (10 min each to build with the factory)
  • Pre-built library entries: ESPN, Flight Goat, Movie Goat, Recipe Goat, Linear, Amazon, Craigslist, eBay, TikTok Shop, Shopify, Hacker News, Contact Goat (LinkedIn → verified email), Airbnb
  • Stack: written in Go (free, fast, agent-friendly); SQLite backend per CLI for local mirroring + no rate limits

Workflow shown

  1. Drop three URLs (printingpress.dev, library repo, factory repo) into Claude Code
  2. Ask it to install — it figures out the Go prereq, runs setup
  3. Either use catalog CLIs directly or invoke the factory skill to build a new one ("here's the site, build a CLI for it")
  4. Wrap each CLI in a Claude Code skill so it's callable via natural language
  5. Optional: package CLI + skill into a private GitHub repo to share with team

Critique / things to verify

  • The 35× / 72% benchmark is not sourced in the video — would be worth tracking down the original Printing Press docs/post.
  • "Just use a CLI" doesn't bypass upstream rate limits or quotas (Nate says this explicitly re: YouTube API).
  • For sites without APIs, the CLI uses real Chrome sessions, which means cookies/auth still need to be managed somewhere — same key-storage problem as MCP, just in a different file.

Cross-links