All videos

    Claude Code MCP & Skills with PrintingPress.dev (Save Tokens)

    Add Claude Code MCP servers and skills with PrintingPress.dev — install, wire them in, and cut Claude Code token usage with agent-native CLIs instead of raw HTTP.

    Share this video

    Claude Code gets dramatically cheaper and smarter once you stop pointing it at raw HTTP APIs and start giving it purpose-built Claude Code skills and MCP servers. PrintingPress.dev prints both for you — from any API spec, or even a website with no public API — alongside a token-efficient Go CLI. This page shows what a Claude Code skill is, how to install Claude Code MCP servers and skills with PrintingPress.dev, and how those two things together cut your Claude Code token usage.

    What is a Claude Code skill?

    A Claude Code skill is a small, installable capability that Claude Code can call on demand — like a custom tool tailored to one job. Instead of Claude reasoning over a giant API surface, it invokes a skill that already knows the right command, the right output shape, and the right defaults. PrintingPress.dev prints a Claude Code skill (plus an OpenClaw skill and an MCP server) for any API in one shot.

    Why Claude Code MCP servers save tokens

    An MCP server exposes capabilities to Claude Code as structured tools. When the MCP server is built around a token-efficient CLI — like the ones PrintingPress.dev prints — Claude reads compact, agent-shaped responses instead of huge JSON blobs. Fewer tokens in, fewer round trips, lower bill.

    How to add skills to Claude Code with PrintingPress.dev

    Every printed binary ships with a ready-to-use Claude Code skill. You copy it into your Claude Code skills folder, restart, and Claude Code picks it up automatically. The exact steps are in the install guide below — it's a single cp command for ready-made library CLIs, or one print + one copy for your own.

    Local SQLite mirror beats a remote API call

    The printed CLIs sync data into a local SQLite mirror. That means Claude Code can run SQL-style queries — joins, filters, aggregates — against your Linear issues, eBay sold comps, or OpenRouter usage in 50ms, without spending tokens on pagination loops or rate-limit retries. The expensive call happens once; every Claude Code query after that is basically free.

    Compound commands instead of ten round trips

    Instead of Claude Code planning five tool calls to find 'every blocked Linear issue whose blocker hasn't moved in 7 days,' the printed CLI exposes that as one compound command. One prompt, one call, one terse result — the biggest single lever for reducing Claude Code token usage.

    How to reduce Claude Code token usage

    Three habits compound: (1) prefer Claude Code skills and MCP tools over raw HTTP, (2) use the printed CLIs' --agent / --llm output modes so responses are compact, (3) push reads to the local SQLite mirror so pagination loops never enter the context window. Together they typically deliver a 5–10x reduction in tokens per tool call.

    How to check Claude Code token usage

    Run `claude /cost` inside Claude Code to see token usage for the current session, or install pp-openrouter from the Printing Press library to query your OpenRouter spend from the terminal. Measure before and after adding a skill or MCP server — the delta is usually obvious within a single session.

    Install Go, PrintingPress.dev, and your first CLI

    PrintingPress prints Go binaries, so Go is the only prerequisite. Once Go is installed, you can install the press itself and then pull any CLI from the library in seconds.

    1. 1. Ask Claude to install Go for you

      Skip the OS-specific dance. Open Claude (or Claude Code in your terminal) and paste the prompt below. Claude will detect your OS, pick the right installer (Homebrew on macOS, apt on Linux, the .msi on Windows), add Go's bin folder to your PATH, and verify the install — all in one go.

      # Paste this into Claude / Claude Code
      Install Go on my machine. Detect my OS, use the best package manager
      for it, add $(go env GOPATH)/bin to my PATH in the right shell rc file,
      then run `go version` to confirm it worked.
      
      # When it's done, verify yourself
      go version
    2. 3. Install PrintingPress.dev

      Install the `pp` command with `go install`. That single binary is what prints new CLIs from an API spec or a website.

      go install github.com/mvanhorn/printing-press/cmd/pp@latest
      
      # Confirm it's on your PATH
      pp --help
    3. 4. Install a CLI from the Printing Press library

      Browse the library at github.com/mvanhorn/printing-press-library and install any printed CLI directly with `go install`. The examples below show a few popular ones — swap in whichever you need.

      # OpenRouter (token usage + model introspection)
      go install github.com/mvanhorn/printing-press-library/library/ai/openrouter/cmd/pp-openrouter@latest
      
      # Linear (local SQLite mirror + SQL queries)
      go install github.com/mvanhorn/printing-press-library/library/productivity/linear/cmd/pp-linear@latest
      
      # Verify install
      pp-openrouter --help
      pp-linear --help
    4. 5. Print your own CLI from an API

      Point `pp` at an OpenAPI spec (or a website) and it prints a Go CLI, a Claude Code skill, an OpenClaw skill, and an MCP server in one shot.

      pp print --spec ./my-api.openapi.json --name my-api
      
      # Then install the freshly printed CLI
      cd ./out/my-api && go install ./cmd/pp-my-api
    5. 6. Install the Claude Code skill and MCP server

      Each printed CLI ships with a Claude Code skill and an MCP server. Drop the skill into your Claude Code skills folder, or register the MCP server in your Claude config, and Claude will start using the token-efficient command instead of raw HTTP.

      # Claude Code: copy the printed skill
      cp -r ./out/my-api/claude-skill ~/.claude/skills/my-api
      
      # Or run the MCP server
      pp-my-api mcp serve

    Frequently asked questions

    How does PrintingPress.dev save tokens with Claude?
    It replaces raw HTTP calls with a purpose-built CLI that returns compact, agent-shaped output. Claude reads less JSON, makes fewer round trips, and can query a local SQLite mirror instead of paginating a remote API — all of which directly reduce input and output token usage.
    Do I need to write the CLI myself?
    No. PrintingPress.dev prints the CLI for you from an API spec — or even from a public website that doesn't expose an API. You also get a Claude Code skill, an OpenClaw skill, and an MCP server in the same command.
    What's the local SQLite mirror for?
    It's a synced local copy of the data behind the API. Claude can run rich queries against it (joins, filters, aggregates) in milliseconds without spending tokens on pagination, rate limits, or repeated fetches. The remote call happens once at sync time.
    Does this work with MCP and Claude Code?
    Yes. Each printed binary ships as a Claude Code skill, an OpenClaw skill, and an MCP server, so you can plug it into whichever agent runtime you're using and Claude will start calling the token-efficient command instead of hitting the API directly.
    Where can I find CLIs other people have printed?
    The printing-press-library on GitHub already has CLIs for Linear, OpenRouter, DigitalOcean, Cloud Run, Render, Shopify, eBay, FedEx, Instacart, TikTok Shop, and more — installable straight from the library.

    Join the conversation

    Like, comment, and shape the next video

    Every like and comment tells YouTube to show this to more people who need it. Pick a prompt below, drop it under the video, and Chad reads (and replies to) every one.

    • "This is the first AI video that actually made sense to me — thanks Chad!"

    • "Just tried this and it worked on the first go. Subscribed."

    • "Would love to see you break down your full workflow next."