perch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| perch_guideA | The short authoring guide for Perch mods: package shape, the Lua declarations (settings/widgets), handlers, scopes, style. Read this first. |
| perch_vocabularyA | The canonical vocabulary (api-spec.json): display components and their props, shared props, color roles, host functions, handlers, scopes, contexts. Pass |
| perch_docsA | The modding and API documentation. Without |
| perch_examplesA | The builtin Perch packages (media, clock, weather, launcher, …) are complete worked examples of the vocabulary. Without |
| perch_validateA | Checks a package folder: mod.json against the manifest schema (id = folder name, no legacy widgets/settings keys, known scopes), the entry exists, every .lua parses, the entry declares a widget, and display |
| perch_runA | Launches Perch with PERCH_MOD_DEV pointed at the folder that contains this package, so the widget appears in Settings → Layout → Widgets and on the notch. Windows only. Set PERCH_EXE if Perch is not installed through Steam. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool addresses a distinctly different aspect of mod development: learning (guide), reference (vocabulary), documentation (docs), examples (examples), verification (validate), and execution (run). No two tools have overlapping purposes, eliminating ambiguity.
All tools follow the same lower_snake_case pattern with the 'perch_' prefix, and the second part is a clear noun or verb. The style is uniform, making the toolset predictable and easy to navigate.
With six tools, the set is compact and every tool has a clear role in the development workflow. This is within the ideal range and each tool earns its place without redundancy.
The tools cover the complete mod authoring loop: guidance, API reference, documentation, examples, validation, and runtime testing. No critical gaps are apparent for the stated purpose of developing Perch mods.