feat(plugins): make CCAM installable straight from a Claude Code plugin
Adds a root `ccam` plugin (`.claude-plugin/plugin.json`, `"source": "./"`) so
`/plugin marketplace add` + `/plugin install ccam@...` is enough on a machine
with nothing but Claude Code: no clone, no npm run setup, no manual npm start.
- scripts/plugin-bootstrap.js: SessionStart hook. Fast-path exit, Node >=22.5
gate (node:sqlite), mkdir lock with stale reclaim, deps installed into
~/.claude/agent-dashboard/runtime/ (never the plugin cache), legacy
checkout-hook cleanup (backed up), ~/.local/bin/ccam launcher, eager UI
build so client routes like /run work immediately, detached server spawn.
- scripts/plugin-open.js, scripts/plugin-doctor.js: /ccam-open, /ccam-doctor.
- server/index.js: DASHBOARD_CLIENT_DIST override (plugin cache is read-only).
- mcp/build/ is committed (plugin MCP servers start before any bootstrap could
build them) and kept honest by scripts/check-mcp-build.js (content hash,
not mtime), enforced by pre-commit when mcp/src changes.
- plugins/ccam-dashboard/.mcp.json moved under plugins/ccam/ with a working
${CLAUDE_PLUGIN_ROOT} path (the old relative path never resolved from a
marketplace-cached subdir).
- Docs: README, INSTALL, SETUP, ARCHITECTURE, CLAUDE.md, docs/PLUGINS.md,
docs/MCP.md, docs/CLI.md, docs/HOOKS.md.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,135 @@
|
||||
/**
|
||||
* @file tool-registry.ts
|
||||
* @description Core functions for registering tools in the MCP server. This module defines the ToolRegistrar type, which is a function that can be used to register a tool with a name, description, input schema, and handler function. It also provides factory functions to create different types of registrars: one that registers tools directly with the MCP server and collects entries for REPL mode, and another that only collects entries without registering with the MCP server (for pure REPL mode). The registrars handle error logging and result formatting to ensure consistent behavior across different tool implementations.
|
||||
* @author Nguyễn Ngọc Trí Vĩ <vinnt@smartgift.vn>
|
||||
*/
|
||||
/* =============================================================================
|
||||
* MODULE_GUIDE — extended in-file reference (comments only; safe to read, never executed)
|
||||
* =============================================================================
|
||||
* **Purpose:** Dashboard module consumed by the React client, MCP tools, or desktop shell depending on deployment mode.
|
||||
*
|
||||
* ## Design constraints
|
||||
* - Local-first: no telemetry leaves the machine unless the user configures webhooks.
|
||||
* - Fail-safe hooks path on the server must never block Claude Code; UI mirrors that
|
||||
* philosophy by degrading gracefully (empty states, stale badges, reconnect loops).
|
||||
* - Destructive flows stay behind explicit confirmation modals and server-side gates.
|
||||
* - Internationalization: user-visible strings belong in i18n JSON, not literals here.
|
||||
*
|
||||
* ## Remote data & SSH
|
||||
* Remote Data Sources let operators aggregate multiple machines. SSH entries describe
|
||||
* how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
|
||||
* scoped GET via `?sources=`. Health checks and import history surface in Settings.
|
||||
*
|
||||
* ## Observability
|
||||
* Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
|
||||
* provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
|
||||
* Docker Compose profiles are documented in `monitoring/README.md`.
|
||||
*
|
||||
* ## Internal dependencies
|
||||
* - `./logger.js`
|
||||
* - `./tool-result.js`
|
||||
*
|
||||
* ## Public surface
|
||||
* - `ToolHandler` — exported API; see TSDoc on the symbol for behavior.
|
||||
* - `ToolRegistrar` — exported API; see TSDoc on the symbol for behavior.
|
||||
* - `ToolEntry` — exported API; see TSDoc on the symbol for behavior.
|
||||
* - `createToolRegistrar` — exported API; see TSDoc on the symbol for behavior.
|
||||
* - `createDualRegistrar` — exported API; see TSDoc on the symbol for behavior.
|
||||
* - `createCollectorRegistrar` — exported API; see TSDoc on the symbol for behavior.
|
||||
*
|
||||
* ## Testing pointers
|
||||
* - Prefer colocated `__tests__` with Vitest + Testing Library for UI.
|
||||
* - Server contract changes require `npm run test:server` and OpenAPI sync.
|
||||
* - MCP edits: `npm run mcp:typecheck` and `npm run mcp:build`.
|
||||
*
|
||||
* ## Related docs
|
||||
* - `ARCHITECTURE.md` — hooks → API → SQLite → WebSocket → UI pipeline.
|
||||
* - `docs/API.md` — REST reference.
|
||||
* - `.claude/skills/file-headers/` — mandatory `@author` header policy.
|
||||
* ============================================================================= */
|
||||
/* -----------------------------------------------------------------------------
|
||||
* EXPORT CATALOG — quick index of symbols defined below (documentation only).
|
||||
* -----------------------------------------------------------------------------
|
||||
* **ToolHandler**
|
||||
* Part of this module's public contract. Downstream imports should treat
|
||||
* the signature and return type as stable unless release notes say otherwise.
|
||||
* When behavior changes, update the `@file` overview and relevant tests.
|
||||
*
|
||||
* **ToolRegistrar**
|
||||
* Part of this module's public contract. Downstream imports should treat
|
||||
* the signature and return type as stable unless release notes say otherwise.
|
||||
* When behavior changes, update the `@file` overview and relevant tests.
|
||||
*
|
||||
* **ToolEntry**
|
||||
* Part of this module's public contract. Downstream imports should treat
|
||||
* the signature and return type as stable unless release notes say otherwise.
|
||||
* When behavior changes, update the `@file` overview and relevant tests.
|
||||
*
|
||||
* **createToolRegistrar**
|
||||
* Part of this module's public contract. Downstream imports should treat
|
||||
* the signature and return type as stable unless release notes say otherwise.
|
||||
* When behavior changes, update the `@file` overview and relevant tests.
|
||||
*
|
||||
* **createDualRegistrar**
|
||||
* Part of this module's public contract. Downstream imports should treat
|
||||
* the signature and return type as stable unless release notes say otherwise.
|
||||
* When behavior changes, update the `@file` overview and relevant tests.
|
||||
*
|
||||
* **createCollectorRegistrar**
|
||||
* Part of this module's public contract. Downstream imports should treat
|
||||
* the signature and return type as stable unless release notes say otherwise.
|
||||
* When behavior changes, update the `@file` overview and relevant tests.
|
||||
*
|
||||
* ----------------------------------------------------------------------------- */
|
||||
import { errorResult, jsonResult } from "./tool-result.js";
|
||||
/**
|
||||
* Creates a {@link ToolRegistrar} that registers each tool directly with a
|
||||
* live `McpServer`. Its handler wrapper is the one place that logs
|
||||
* `debug`-level start/completion (or `error` on failure), converts a
|
||||
* success into a `CallToolResult` via {@link jsonResult}, and catches any
|
||||
* thrown error — converting it via {@link errorResult} — so a failing call
|
||||
* always resolves rather than rejects the MCP request.
|
||||
*/
|
||||
export function createToolRegistrar(server, logger) {
|
||||
return (name, description, inputSchema, handler) => {
|
||||
server.registerTool(name, { description, inputSchema }, async (args) => {
|
||||
try {
|
||||
logger.debug("Tool invocation started", { tool: name });
|
||||
const result = await handler(args);
|
||||
logger.debug("Tool invocation completed", { tool: name });
|
||||
return jsonResult(name, result);
|
||||
}
|
||||
catch (error) {
|
||||
logger.error("Tool invocation failed", {
|
||||
tool: name,
|
||||
error: error instanceof Error ? error.message : "Unknown error",
|
||||
});
|
||||
return errorResult(error);
|
||||
}
|
||||
});
|
||||
};
|
||||
}
|
||||
/**
|
||||
* Registrar that also collects tool entries for REPL mode. Delegates to
|
||||
* {@link createToolRegistrar} and additionally pushes a plain
|
||||
* {@link ToolEntry}, so one call would both register a tool AND make it
|
||||
* directly invokable. Not currently used — `index.ts` builds REPL entries
|
||||
* via {@link createCollectorRegistrar} instead.
|
||||
*/
|
||||
export function createDualRegistrar(server, logger, collector) {
|
||||
const mcpRegistrar = createToolRegistrar(server, logger);
|
||||
return (name, description, inputSchema, handler) => {
|
||||
mcpRegistrar(name, description, inputSchema, handler);
|
||||
collector.push({ name, description, handler });
|
||||
};
|
||||
}
|
||||
/**
|
||||
* Registrar that only collects (no MCP server, for pure REPL mode). Used by
|
||||
* `collectAllTools` to build the REPL tool list with no protocol overhead —
|
||||
* thrown errors propagate as real exceptions to the REPL's own try/catch.
|
||||
*/
|
||||
export function createCollectorRegistrar(collector) {
|
||||
return (name, description, _inputSchema, handler) => {
|
||||
collector.push({ name, description, handler });
|
||||
};
|
||||
}
|
||||
Reference in New Issue
Block a user