Plugins

A plugin is a WebAssembly module PeckBoard loads to add tools, pages, and behaviors without changing the core binary — for example a diff viewer on every project, or SSH tools for a fleet of servers. Plugins install in a couple of clicks from a built-in registry, and none of a plugin’s code runs until you approve exactly the capabilities it asked for. This page covers installing plugins and lists every plugin in the official registry; each one has its own page with a screenshot, its MCP tools, and its settings. Session Hooks maps the points where a plugin can hook into a running session, and the MCP Server Catalog lists the external tool servers the registry can configure alongside plugins.

Installing and Updating

Open Settings → Plugin Registry to browse the registry. Installing downloads the plugin into the data directory, verifies its checksum and that your PeckBoard version is new enough, and loads it inert: it cannot act yet. An approval dialog then lists the exact hooks and permissions the plugin requests — approve to activate it, deny to keep it dormant. Updating an installed plugin follows the same flow, and an agent session can install or update one for you with the upgrade_plugin tool.

The plugin registry's Browse tab listing installable plugins and MCP server templates, with search, kind, and category filters

graph LR
  R[Registry] -->|download + verify| I[Installed, inert]
  I -->|you approve its hooks| A[Active]
  I -->|you deny| D[Dormant]
Where plugins live and how approval is tracked

Installed plugins are single .wasm files in <data-dir>/plugins/, loaded at startup into a sandbox with no filesystem or network of its own — every capability a plugin uses is a host function gated by a permission it declared. Approval is recorded against the plugin’s exact hook and permission set, so an update that asks for different capabilities drops back to pending and asks again; an update with unchanged capabilities stays approved. Uninstalling deletes the .wasm and clears the plugin’s stored approval and settings, so a reinstall starts clean.

Plugins that need configuration declare settings fields in their manifest; PeckBoard renders a form for them on Settings → Plugins — click the plugin’s row — and stores values per plugin. The same values can be provided in config.json under plugins.<id>.config, which wins over the UI on every start.

The AI providers (Claude, Codex, Cursor, Grok, Kimi, Ollama, OpenAI-Compatible, Mock) are also plugins — first-party ones compiled into the binary, activated from the same registry page. The Providers page covers them. One historical note: the standard worker tools (file reading and editing, search, git, web fetch, run_command, run_tests, math) were once a plugin called common-tools but are now part of core — every session has them with nothing to install.

What Each Plugin Adds

Every plugin in the official registry. The name links to the plugin’s page, which lists its MCP tools, settings, permissions, and prerequisites.

Plugin What it adds MCP tools
App Manager Install and remove developer apps on the host and SSH targets, with a dashboard 7
Chicken Coop A 3D chicken run visualizing every live session as a bird —
Diff Viewer A side-by-side diff and editor for every repo in the folder, on projects and sessions —
GitHub Bridge GitHub issues synced with kanban cards, PR links, auto-close on done 4
Graphify A queryable code knowledge graph per repo, with a visualizer page 3
HomeKit HomeKit Wi-Fi/Ethernet accessories and Philips Hue lights, rooms and scenes, from a page and agents 13
Kaiad Kaiad control-plane access from any session 4
Nginx Proxy Manager Nginx Proxy Manager control from any session 4
Notifier Lifecycle events forwarded to ntfy, Telegram, Discord, and webhooks —
OpenAI-Compatible Provider Any /v1/chat/completions endpoint as an AI provider —
OpenSearch Query and manage an OpenSearch or Elasticsearch-compatible cluster 8
PR Review Parallel multi-model branch reviews, triaged and posted to the GitHub PR with your decision 14
Print Farm 3D printer fleet control (Klipper, OctoPrint, Prusa, Bambu) with OrcaSlicer slicing and 3D preview 9
Playwright Tests Replay of recorded browser test runs, with MP4 export —
Pre-hatcher Opt-in enrichment of chat messages with repository context before the main model sees them 1
Project Planner A project definition built by interview, one question per slide 4
Public API A public REST API with scoped API keys —
Session Control Tools for controlling other sessions, plus goal-driven orchestrators 14
SSH Fleet A registry of SSH hosts, remote command and file tools, and a live dashboard 10
UI Gauge UI design scoring against user-ranked baselines, with a learned style prompt 5

MCP Server Catalog

Besides WASM plugins, the registry lists ready-made MCP server entries — over a hundred external tool servers such as Playwright, GitHub, Postgres, and Figma that sessions can talk to directly. Adding one from the registry configures it without hand-writing the server command or URL. The full list, grouped by category, is on the MCP Server Catalog page.

To use MCP servers outside PeckBoard — from scripts or a chat bot — install mcpx from App Manager. It is a command-line MCP client and local gateway that reads the mcp.json format used by Claude, Cursor, and VS Code (not the servers configured in PeckBoard) and handles OAuth. It can also call PeckBoard’s own tools through an External Access client.

Table of contents

Assembled with many small pecks.

This site uses Just the Docs, a documentation theme for Jekyll.