Build and publish a landing page with OpenCode

Check which OpenCode version you are configuring

This guide targets OpenCode v2’s documented configuration. Older OpenCode examples use a different MCP shape, so confirm your installed major version before copying settings. This is a documentation-based workflow reviewed on September 15, 2026, not a report of a live OpenCode-to-Pageree account test.

OpenCode can help create the page source while a remote publishing service handles hosting and enquiries. Choose the business job first. A simple campaign asking for a project enquiry has different requirements from a web app with accounts, payments, and persistent application data.

Add the remote server using the v2 structure

In your project’s existing opencode.jsonc, add Pageree under mcp.servers:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "pageree": {
        "type": "remote",
        "url": "https://mcp.pageree.com/"
      }
    }
  }
}

Keep other project settings intact. Start the authentication flow with:

opencode mcp auth pageree

In v2, /mcps opens server management in the interactive client. Remote OAuth is enabled unless explicitly disabled; do not add oauth: false for this sign-in route. See OpenCode v2’s official MCP documentation for the current schema and commands.

Complete browser authorization, then ask OpenCode to read the Pageree account and list existing pages. An actual response verifies that this session can use the tools. If your installed version does not recognize mcp.servers or /mcps, use its matching documentation instead of combining v1 and v2 examples. The endpoint itself remains the root address in Pageree’s connection guide.

Write a brief suited to a single page

For an illustrative example, consider a founder offering a technical setup review to small online businesses. The goal is to understand a prospective client’s problem before discussing a project.

Build a landing page for my technical setup review service.
Audience: small online businesses with disconnected tools and manual handoffs.
Offer: review one workflow and provide a written map of practical improvements.
Goal: a qualified enquiry, not an instant integration or guaranteed savings.
Use the supplied brief and authorized assets. Ask for missing factual details.
Do not invent client logos, supported integrations, prices, or testimonials.
Follow Pageree's current page, asset, form, privacy, and publishing skills.
Write one complete HTML document with inline CSS and JavaScript and hosted images.
The form should collect name, email, business website, and the workflow problem.
Ask me for the destination inbox and chosen slug. Save a private preview.
Keep the page ID in this project and wait for my review before publication.

Tell OpenCode to inspect the project before adding dependencies. Pageree’s single-document route does not need a local application server. If you are reusing an existing framework project, ask for a dependency assessment before assuming its output can be hosted unchanged. The HTML hosting guide explains the boundary.

Review the real preview

Check the generated file for local asset paths, unfinished placeholder text, and form handlers that only display a success message. Then open the private preview in a browser. Inspect mobile wrapping, contrast, keyboard focus, required fields, and the explanation of what happens after an enquiry.

If OpenCode has a browser tool, ask it to report exactly what it inspected. If it does not, review the browser yourself. A terminal agent can reason about markup without having seen the rendered page; that distinction matters when deciding whether a layout is ready.

Approve publication only after reviewing the preview. Open the public URL and send a clearly marked test enquiry using an address you control. Verify the expected destination receives it. The form-to-email guide provides a useful first delivery check before adding a more complex automation.

Return to the same page later

Store the page ID, slug, and public URL with the project. When the offer changes, ask OpenCode to retrieve current page information and the appropriate stored source. An open draft may contain newer work than the live version or your local file.

Save the complete revised HTML on the same page ID, review the preview, and publish the approved change. This preserves one campaign address and a usable version history. The live-update guide shows how to scope that request and avoid accidental duplicate pages.