lpmoo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LPMOO_MCP_MODE | No | Controls server mode. `local` or `stub` runs the offline section stub. `remote` returns `mcp_byo_bridge_pending` and makes no network request. Any other value is rejected. | local |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_templatesA | List LP direction recipes the canvas can generate from. No model call. |
| get_recipeA | Return ordered section structure for a recipe id (type, title, job). No copy, no HTML. |
| generate_lp_sectionsB | Generate an ordered Section array (type, spec, rationale) from a brief and structure constraints. Never return a full-page HTML document. |
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 3 tools
Each tool has a distinct role: list_templates enumerates available recipes, get_recipe retrieves structural details for a specific recipe id, and generate_lp_sections performs generation from a brief. The required inputs and verbs make misselection unlikely.
All three names follow a consistent verb_noun snake_case pattern. The only minor drift is terminology between 'templates' and 'recipe', but the naming style itself is predictable.
Three tools are well-scoped for a narrow LP section-generation server: discovery, structure inspection, and generation. No tool appears redundant or extraneous.
The surface covers the core lifecycle of listing recipes, inspecting a recipe structure, and generating sections. It lacks explicit validation or refinement operations, but those are not clearly required for the stated generation-focused purpose.