mrkeyoor.comAsk

mvanhorn/cli-printing-presstested 08 Oct 2026commit 281c6b3

cli-printing-press review

CLI Printing Press merits a supervised evaluation when API research, generated CLI and MCP interfaces, and local data commands are part of the job.

  • Install 38 s
  • Build 228 s
57/63passed, run exited non-zero
  • 101 packages
Dev Toolsevaluationupdated 31 Oct 2026
+29stars / 7d

Evaluate CLI Printing Press if you need an agent workflow for building API tools and can review its generated code before use. The README describes generating a Go CLI and an MCP server from an API specification or discovered website traffic. Our run on October 8, 2026, at commit 281c6b3 recorded successful installation and build, followed by a failing test command. It did not establish that the complete generation workflow or a generated tool worked against a live service.

Verdict

CLI Printing Press merits a supervised evaluation when API research, generated CLI and MCP interfaces, and local data commands are part of the job. Our sandbox built the repository but returned a failing test command; it did not validate a complete generated tool. Start with an isolated target and verify one useful task, including cleanup where writes occur. Choose a contract-based generator when client bindings or server boilerplate are the whole requirement.

We ran it

Lab card: what happened when we ran cli-printing-press
Lab card from our sandbox run
Screenshot of cli-printing-press (github.com/mvanhorn/cli-printing-press)
github.com/mvanhorn/cli-printing-press
Install✓ · 38s101 packages
Build✓ · 228s
Tests✗ · 676s57 passed · 6 failed of 63 (go test)
Repo2110 files~514,717 lines of source · 28.6 MB · 10 CI workflows

Answers from our run

Does cli-printing-press build from source?

Dependencies installed in 38 seconds (101 packages), and the build succeeded in 228 seconds. We cloned commit 281c6b3 into a clean Debian container with 3 CPUs and no project-specific setup.

Do cli-printing-press's tests pass?

No. The project's own test command finished in 676 seconds and reported 57 passed, 6 failed (go test).

Who should not use cli-printing-press?

Teams whose entire requirement is generating client bindings from an existing OpenAPI document.

What are the alternatives to cli-printing-press?

OpenAPI Generator, oapi-codegen. CLI Printing Press merits a supervised evaluation when API research, generated CLI and MCP interfaces, and local data commands are part of the job.

Setup2/5Installation and build succeeded in our stored run, but tests returned exit code 1. The separate binary-and-skills setup and complete agent workflow were not validated.
Docs3/5The README documents prerequisites, agent installation, output locations and verification stages, but mixes those instructions with unverified quality and token-saving claims.
Community3/5Last push on 2026-08-26 and 4,997 stars.Editor’s note: The supplied extracts do not establish contributor breadth, sustained support quality or representative issue response times.
Maturity2/5The repository builds, but its test command failed and generated-tool behavior remains unverified. The historical NAS report is closed; our run did not validate its fix.

How we score

Discussed on

  1. hnCLI Printing Press – create go CLI tool from any API7 points

Who it’s for

Developers repeatedly building API tools for coding agents.
Teams interested in generated CLI and MCP interfaces, with local SQLite storage where the target warrants it.
Reviewers who can inspect generated commands, authentication, data flow and cleanup behavior.
Claude Code users evaluating the README's best-tested skills workflow.

Who it’s NOT for

Teams whose entire requirement is generating client bindings from an existing OpenAPI document.
Users expecting our repository build result to certify generated tools for production.
Operators who cannot isolate live verification from valuable accounts or devices.
Teams requiring measured token savings, runtime performance or security assurance from this review.

Setup reality

In our sandbox, installation took 38 seconds and returned exit code 0; the build took 228 seconds and returned exit code 0. The test command took 676 seconds and returned exit code 1 without timing out. These are the attached harness's rounded durations for the stored October 8, 2026 run at commit 281c6b3, not a new execution.

The matching README requires Go 1.26.6 or newer, Node/npm for npx, and Claude Code or another supported agent. The install log records downloading Go 1.26.6 despite the sandbox's golang:1.24-bookworm base image. The current README instead requires Go 1.26.10 or newer; that requirement must not be projected backward onto our run.

The documented workflow needs both the generator binary and the Printing Press skills. Restart or reload the agent after refreshing skills. Claude Code is the best-tested path according to the README; a Codex installation path is also documented. Our stored command outcomes do not verify either agent's complete workflow.

What our sandbox established

Our run on October 8, 2026, at commit 281c6b3 installed and built the repository, but its test command failed. The sandbox had 3 CPUs and 8 GB of memory. Installation took 38 seconds, the build took 228 seconds, and tests took 676 seconds.

Our harness records each command's success flag, exit code, elapsed time, timeout status and retained output tail. It separately stores parsed test summaries. The build record reports exit code 0 and a tail of vet-exit:0; the test record reports exit code 1 with no timeout. A successful build command does not demonstrate a completed agent task, a deployed MCP server or a working generated CLI.

The stored parser summaries report 57 passing and 6 failing package entries, with a total of 63. These are not counts of individual test cases, and they do not establish exhaustive unique coverage. The raw metrics separately record 2 packages without test files. We have not added those to the stored total or treated them as failures.

The retained output names failures in internal/cli, internal/generator and internal/openapi. It also contains Error: public parameter audit has 1 pending finding(s). That message does not establish a dependency vulnerability or explain every failing package. The excerpt does not reconcile all 6 stored failure entries, so we cannot assign a cause to each one.

The MrKeyoor testing methodology explains how command outcomes and parsed counts reach a review. Its current description provides provenance context; it does not establish which methodology revision governed this older run. This correction uses the stored record and performs no new execution.

What the generator is intended to produce

The README describes generating a Go CLI and an MCP server from an API specification or discovered website traffic. Research, generation, verification and publication are parts of the documented workflow. The binary and agent skills are separate components, with skills described as the primary interface.

The project's proposed advantage is the work surrounding endpoint bindings: researching an API, producing agent instructions, adding local data storage and building commands that combine resources. The README describes domain-specific SQLite tables, full-text search and incremental sync for suitable entities. Those are documented capabilities, not behaviors demonstrated by our sandbox run.

Choose an evaluation target that needs this additional workflow. If your task ends at generating client types and HTTP methods from a known contract, the alternatives below address that narrower requirement directly. We did not measure the README's token-saving claims, compare generated quality or benchmark local queries.

Live verification needs a separate acceptance check

Issue 4355 reports that dogfooding a Synology CLI with CLI Printing Press 4.29.0 created folders on a real NAS and left them behind. The report says a cleanup command returned success although nothing was deleted. This is a historical report about that version and target, not an observation from our sandbox.

GitHub marks issue 4355 closed as completed through PR 4735 on September 17, 2026. The supplied issue extract does not show the implementation of that fix, and our run did not validate it. The report therefore supports a concrete acceptance check: use a disposable target, identify any resources created during verification, and read them back after cleanup to confirm removal. An exit code alone cannot answer that question.

The README describes its optional live smoke phase as read-only. Keep that documented phase distinct from the dogfood behavior reported in the issue. Our repository test result establishes neither live phase's behavior for a generated tool.

No independently fetched extract for issue 4358 was supplied, so this review makes no finding about generated shell guidance based on that issue. The stored dependency audit is null, and scan coverage is unknown. Neither the build result nor the presence of a package named govulncheck establishes a completed security scan.

When another generator fits better

OpenAPI Generator generates client libraries, server stubs, documentation and configuration from an OpenAPI specification. Choose it when those outputs are your requirement. This is an alternative for contract-based generation, not evidence that it reproduces Printing Press's research or local-data workflow. Its README also warns users to review untrusted specifications, templates and other inputs; choosing it does not remove the need to review generation inputs.

oapi-codegen converts OpenAPI specifications into Go server implementations, API clients or HTTP models. Choose it when you want Go code to integrate into an application you maintain. Its README distinguishes its client output from a fuller SDK approach and warns that development documentation can describe unreleased changes. Check the documentation for the version you select.

These comparisons concern documented roles. We did not run either alternative or compare reliability, speed or output quality. For readers looking to install an existing generated tool rather than build one, the supplied Printing Press Library page answers a different question: finding and installing service-specific CLIs.

How to read our ratings

Assessed dimensions use integers from 1 to 5: 1 means substantial observed obstacles, 2 means usable steps with significant unresolved friction, 3 means adequate evidence with material limits, 4 means strong documented support with minor gaps, and 5 requires broad direct evidence with few material gaps. Each dimension uses evidence relevant to that dimension; stars do not establish support quality or adoption. Unassessed means the supplied evidence cannot support a rating.

Setup ease is 2 because installation and build succeeded while the test command failed, and the agent workflow remains unverified. Documentation is 3 because the README explains prerequisites, output locations and verification stages, but mixes operational instructions with performance and quality claims our run did not test. Maturity is 2 because the repository builds, yet the failing tests and unverified generated behavior leave substantial evaluation work. Community is unassessed because the supplied extracts do not establish contributor breadth, response quality or sustained support.

A useful first evaluation

Pick one API and one task that needs more than endpoint bindings. Review the generated authentication, command behavior and local data flow, then test that task in an isolated account. If verification writes resources, check their removal by reading the target afterward. Accept the tool based on that task's observed behavior, rather than the generator's scorecard or our repository build result.

Alternatives

ProjectWhat it isPick it when
OpenAPI Generator gh↗Generates API client libraries, server stubs, documentation and configuration from an OpenAPI specification.Choose it when you have an OpenAPI contract and need those generated artifacts. It is an alternative for that narrower task; we did not test it as a replacement for Printing Press's complete agent workflow.
oapi-codegen gh↗Converts OpenAPI specifications into Go server implementations, API clients or HTTP models.Choose it when you want Go bindings or server boilerplate inside an application you maintain. Check the selected release's documentation rather than assuming development-branch features are released.

What people are saying

  1. [github-trending] mvanhorn/cli-printing-press

Sources

  1. CLI Printing Press repository and README
  2. CLI Printing Press v4.31.1 release
  3. Dogfood harness side-effect report
  4. Generated shell guidance report
  5. Generated help and exit-code defects

More dev tools reviews