Claude-Code

A Reusable Access Layer I first built pages, a static-site host with an MCP upload tool. It was useful enough that I kept repeating the design. The cluster now has ten MCP servers: congress-mcp, freshrss-mcp, googlenews-mcp, gsc-mcp, jetlog-mcp, media-mcp, monica-mcp, nodebyte-mcp, pages, and the Kubernetes server. Each server fronts one self-hosted application. The similarity is intentional. They share the manifest layout, bearer-token boundary, hostname convention, and deployment path. Adding the tenth took about forty minutes, most of it spent writing the tool descriptions that decide whether a client can use the server sensibly. ...

Introduction I use Claude Code for substantial one-off analysis, and its output is frequently a single self-contained HTML file. Examples include a flight-log dashboard, an interactive trainer derived from an audiobook transcript (described in Building Interactive Trainers From My Audiobook Library), a pedigree chart, and a client map. Each began either as a Live Artifact or as a file in /tmp that I opened with file://, inspected once, and subsequently lost. ...

Building Interactive Trainers From My Audiobook Library I listen to a considerable number of business and leadership audiobooks, yet retain very little of their content a month later. Listening is passive; useful frameworks blur together with time; and “I read that one” readily becomes “I think I read that one.” I wanted the retention without replaying seven hours merely to recover the one idea I needed. I therefore built a compact production process that converts an audiobook into an interactive trainer, in which each concept and example becomes a card supporting three modes: Browse, Flashcards, and Quiz. Each book receives its own self-hosted site on my internal network; during a single afternoon, I applied the process to seven titles. ...