Developers · Configuration¶

There is no config:/modules/h1-mcp. This module is configured in three places: environment variables (the LLM provider and its key), light-module YAML (the app, the endpoints, the tool registrations, the decorations) and constants in code for the conversation and loop limits. The tools it exposes are configured by whichever module owns them.

Environment¶

Read by LlmClientFactory the first time a chat request needs a client, then cached for the life of the JVM.

The chosen provider and model are logged once, at client creation: AI provider: Claude (model: …).

The AI Chat¶

The endpoint¶

message is required (400 without it). A missing sessionId gets a fresh UUID, returned in the answer so the client can keep the thread. 503 means the provider is not configured; 500 carries the exception message.

The MCP protocol surface¶

Two endpoints implement the same protocol against different registries:

Error codes: -32600 (no method), -32601 (unknown method), -32602 (missing params or name in tools/call), -32603 (internal error). A tool failure is not a JSON-RPC error: it answers 200 with isError: true and Error: <message> as the text, so the model sees it.

The five tools¶

Registered by this module in h1McpTools/. Their contract with the model is getDescription() plus getInputSchema(); what follows is the action surface.

website¶

Its field contract, all read from the template's dialog at runtime:

• A component's own fields go in properties; nested components go in areas. An object with a templateId inside properties is rejected — that is the one place where FormDrivenNodeIO is constructed with rejectNestedComponents = true.
• A multi-entry field (jcrMultiField) takes an array of objects and a write is a full replace; list_templates marks it "multiple": true and get_page reads it back as an array rather than as the raw links0, links1 children.
• A multi-select scalar (checkBoxGroup, twinColSelect) takes an array of plain values, also a full replace.
• A field whose list_templates entry carries "valueFormat": "path" and a referenceSource is a reference: the value must be the target node's full path, and referenceSource names the workspace and root path where the candidates live.
• A component's node name (0, 1, 2) is an id, not a position. Order is the JCR child order; get_page reports both name and a 0-based order.

asset¶

list, get, upload, update, create_folder, delete_folder, move, rename, reorder, publish, unpublish, delete, remove_property.

content_type¶

Its description tells the model explicitly: if a dedicated tool exists for that content type, use that one; this is for discovery and for content types with no tool of their own.

marketing_tag¶

Standard content-type actions plus the fields of the DX Core marketingTag type — name, dashboardUrl, activeAuthor, placeToPut (headerScripts|bodyBeginScripts|bodyEndScripts), content, pageTemplate, cookies — and pageLink, a list of {path, insertInSubPages} that restricts the tag to specific pages (empty means every page).

pageLink is excluded from the automatic schema and bind, and read and written by hand as indexed mgnl:contentNode children, the same treatment a composite multi-field gets elsewhere. On update it is only touched when the payload contains it.

The class deliberately imports no info.magnolia.marketingtags.* type: everything it needs about the form comes from generic introspection, so this module still compiles without DX Core. And isAvailable() opens a session on the marketing-tags workspace — if the module is not installed, the tool hides itself instead of being listed and failing on use.

h1mcp_keywords¶

Note — these fields are emitted nowhere: no meta tag, no sitemap, no llms.txt, no headless endpoint. The tool is a store; the editorial judgement lives in the agent that reads it. It does not evaluate, recommend or generate keywords, and get on content with none returns empty lists without inferring anything.

REST reference¶

Base path /.rest. Everything is application/json unless noted.

The chat UI¶

Module components¶

Registered as singletons in META-INF/magnolia/h1-mcp.xml, component set main:

McpSessionManager · LlmClientFactory · AiConversationManager

The tools are deliberately not components. They are registered as definitions in h1McpTools/ and instantiated by node2bean, which is why they take their collaborators with Components.getComponent rather than @Inject. H1McpModule implements ModuleLifecycle: it logs on start, removes the obsolete filter node, and shuts the session manager down on stop.