Wrap a local ops dashboard in a read-only MCP server for Claude Code

HomoFuturus had Claude Code build a five-tool, GET-only MCP server over their Mac bot dashboard in under three minutes, then used it to spot bots that only looked like they were running.

Done withClaude Code· Nov 21, 2026

What they did

HomoFuturus runs twenty-plus Claude sessions and a set of bots on a MacBook, watched by a home-made web dashboard called Mac Station that has a local JSON API. They wanted every Claude session to be able to ask what was running. Using Claude Code on Opus 5.5 and writing no code themselves, they first had it build a small warm-up server reporting disk, memory, battery and top processes. Then they asked for a read-only MCP server over the dashboard API with tools for running bots, requests waiting on them, the next 12 hours of schedule, supervisor status and machine resources. The prompt told it to inspect the API with curl before designing tools, to allow GET only, and to register the server at local scope.

How it went

The warm-up server took about a minute. The dashboard server took 2 minutes 58 seconds: five tools, each tested against the live API, with a fixed allowlist of endpoints and no way to stop bots or reply. Asked from a fresh folder which bots were running, Claude called the server four times and answered in 15 seconds. The dashboard showed six bots running; Claude called only three clearly alive, checking for a live process, tmux session or launchd job, and flagged stale timeline entries the author had skimmed past. It also marked its reading of two undefined role tags as a guess.

Worth knowing

The author tested this in a clean macOS virtual machine. Making writes impossible in the server, rather than trusting the agent, is the design point; stopping bots stays a manual job on the dashboard. A server registered with an absolute path breaks if the folder moves, and a local-scope server with the same name overrides the user-scope one inside that project.

Try it

With Claude Code· 6 parts to fill in

My app [app name] has a local API at [base URL] with endpoints [list of endpoints]. Look at the shape of each response with curl first. Then build a read-only MCP server called [server name] in this folder with tools for [the questions I want to ask, e.g. what is running, what is waiting for me, what is scheduled next]. Use GET requests only, to a fixed list of endpoints, and add no action that starts, stops, deletes or sends anything. Return a clear error when the app is not reachable, and summarise long lists instead of passing raw data. Test every tool against the live API, then register the server at [local or user] scope and stop to show me the tool list.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related