toolhive-cloud-ui CLAUDE.md

A set of Claude Code instructions for ToolHive Cloud UI, an open-source Next.js application that displays and manages MCP servers. It documents the project structure, technologies, backend services, authentication, testing, and code-quality tools.

In plain words
What is it for?
It is for developing the ToolHive web interface, including its catalog, server details, tool listings, authentication, API integration, tests, and code formatting.
Why use it?
It gives an AI coding assistant the project context and constraints needed to suggest changes that fit the existing application architecture.

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-cloud-ui/claude-md
Clone the repo
git clone --depth 1 https://github.com/stacklok/toolhive-cloud-ui
Per session 3,539 This file is loaded in full into every session.
When invoked 3,539 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.03539 $0.03539
Opus 5 $0.01769 $0.01769
Sonnet 5 $0.00708 $0.00708
Haiku 4.5 $0.00354 $0.00354

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

Security

Grade A, and why

toolhive-cloud-ui 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 · 368 lines

How it starts

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

Claude AI Assistant Guide - ToolHive Cloud UI

This document provides context and guidelines for Claude (and other AI assistants) working on the ToolHive Cloud UI codebase.

Project Overview

ToolHive Cloud UI is an open-source Next.js 16 application for visualizing and managing MCP (Model Context Protocol) servers running in user infrastructure. It provides a catalog interface with detailed server information, tool listings, and URL copy functionality.

Repository: https://github.com/stacklok/toolhive-cloud-ui
Backend API: https://github.com/stacklok/toolhive-registry-server
License: Apache 2.0 (Open Source)

Core Technology Stack

  • Framework: Next.js 16.0.3 (App Router)
  • React: 19.2.0 with React Compiler (babel-plugin-react-compiler)
  • TypeScript: Strict mode enabled
  • Styling: Tailwind CSS 4
  • UI Components: shadcn/ui
  • Authentication: Better Auth (OIDC, stateless JWT)
  • API Client: hey-api (@hey-api/openapi-ts) with React Query
  • Testing: Vitest + Testing Library
  • Linting: Biome (replaces ESLint + Prettier)
  • Package Manager: pnpm

⚠️ Critical: Validate Against Next.js Documentation

Before suggesting any code or architecture changes:

  1. Consult Next.js Documentation - Verify your approach is correct
  2. This is App Router, not Pages Router - Different conventions and patterns
  3. Validate Server vs Client boundaries - Understand what runs where
  4. Check built-in features - Next.js provides routing, caching, data fetching, etc.
  5. Don't reinvent the wheel - Use Next.js conventions and built-ins

Common mistakes AI assistants make with Next.js:

  • ❌ Mixing Pages Router and App Router patterns
  • ❌ Creating custom routing when file-system routing exists
  • ❌ Not understanding Server Components (no hooks, no event handlers)
  • ❌ Adding 'use client' everywhere or forgetting it when needed
  • ❌ Ignoring Next.js caching and revalidation mechanisms
  • ❌ Using old data fetching patterns (getServerSideProps, getStaticProps)

Read the full file on GitHub · 368 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 · 368 lines · 3,539 tokens per session scan A 1b673e56d432

Subscribe to this mod's changes

toolhive-cloud-ui CLAUDE.md is an instructions file published in the GitHub repository stacklok/toolhive-cloud-ui (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 3,539 tokens to every session, about $0.0177 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-31.