LPmoo has been developed as a web service for structuring landing pages and shaping their copy. In July 2026, we are changing its delivery direction: from a standalone web generator toward creation tools an agent can use through MCP.
The work starts before the generator
Making a page involves reading material, finding the product story, reviewing alternatives and refining language. When that work already happens in an agent, transferring the context into another service adds friction.
Focus on what LPmoo should provide
We are moving away from duplicating a standalone model API integration inside LPmoo. Instead, we want to focus on production steps and outputs: tools a compatible MCP host or agent can call to shape structure, copy and a page within an existing workflow.
MCP does not remove model requirements
This does not mean that models, APIs or authentication are universally unnecessary. Supported hosts, permissions and model access depend on the environment. The design question is whether LPmoo needs to build and maintain a separate connection layer of its own.
A new entry point, the same production problem
What should the product communicate, to whom and in what order? Those questions remain central. As we move closer to agent-based workflows, we will keep working on outputs people can inspect, revise and use. Details of the transition will follow as the pieces are ready.