toolhive-studio CLAUDE.md

Repository guidance for ToolHive Studio, an Electron desktop app for managing MCP servers. It documents the project, required tools, development commands, and generated code that must not be edited by hand.

In plain words
What is it for?
Use it when installing dependencies, starting the app, checking types, linting, formatting, running tests, running end-to-end tests, finding unused code, or regenerating the API client.
Why use it?
It gives coding agents the project context and exact checks to run, reducing setup mistakes and changes that conflict with generated files or version requirements.

Instructions file

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/stacklok/toolhive-studio/claude-md
Clone the repo
git clone --depth 1 https://github.com/stacklok/toolhive-studio
Per session 1,205 This file is loaded in full into every session.
When invoked 1,205 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.01205 $0.01205
Opus 5 $0.00602 $0.00602
Sonnet 5 $0.00241 $0.00241
Haiku 4.5 $0.00120 $0.00120

Measured 2d ago against content hash 38e28da54acc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

toolhive-studio CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

This file provides guidance to Claude Code when working with this repository.

Project Overview

ToolHive Studio is an Electron desktop application for managing MCP (Model Context Protocol) servers. Built with React, TypeScript, and Vite. The Electron app bundles the ToolHive CLI (thv) binary.

Build and Development Commands

pnpm install              # Install dependencies
pnpm run start            # Start dev server with hot reload
pnpm run lint             # Run ESLint
pnpm run type-check       # TypeScript checking (both app and node configs)
pnpm run format           # Format with Prettier
pnpm run test:nonInteractive  # Run unit tests once
pnpm run test             # Run unit tests in watch mode
pnpm run test:coverage    # Unit tests with coverage
pnpm run e2e              # Package + run Playwright e2e tests
pnpm run knip             # Detect unused code
pnpm run generate-client  # Fetch OpenAPI spec + regenerate API client

Husky/lint-staged automatically run lint + format on staged .ts/.tsx files. Run pnpm run type-check manually before committing — it is not covered by the hook.

Environment Requirements

  • Node.js >=24 <25 (use nvm use.nvmrc is present)
  • pnpm package manager
  • Docker daemon must be running (required by ToolHive)

Common Gotchas

  • Docker must be running before pnpm run start — ToolHive manages containers, so the daemon is required even in dev
  • Node version mismatch: wrong Node version can break other native modules. Always nvm use first
  • Stale generated types: if type errors reference API types, run pnpm run generate-client to refresh
  • Electron test runner: unit tests run through Electron (vitest:electron), not plain Node — required for native module compatibility
  • All commands from root: always run pnpm commands from the repository root, not from subdirectories

Auto-Generated Code — Never Edit Manually

These files are generated and will be overwritten:

Read the full file on GitHub · 104 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 104 lines · 1,205 tokens per session scan A 38e28da54acc

Subscribe to this mod's changes

toolhive-studio CLAUDE.md is an instructions file published in the GitHub repository stacklok/toolhive-studio (163 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,205 tokens to every session, about $0.0060 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.