About Enjoyable

Software should be lighter than the problem it solves.

Enjoyable builds small, serious developer tools for gaps that are too painful to ignore and too narrow for a platform to solve well.

The work starts one step before the workaround.

The useful product is often hiding in the script everyone rewrites, the manual check everyone forgets, or the configuration drift everyone accepts. We turn that recurring friction into a maintained utility with explicit boundaries.

What every Enjoyable utility should feel like

Immediate

A developer should reach the first useful result without adopting a platform or rebuilding their workflow.

Legible

The tool should make its plan, authority, evidence, and failure state easier to understand than the problem was.

Durable

A small surface still deserves deterministic behavior, careful recovery, maintained releases, and honest support boundaries.

The first product family tackles MCP friction.

mcp-doctor helps server authors find failures before agents depend on them. mcp-sync keeps local client configuration from drifting. They share a standard of focus, not a requirement that every future product use MCP.

See the utilities