Build a landing page with Cursor and receive enquiries

Build the page inside the editor you already use

Cursor is a useful starting point when your business page lives beside other project files and you want to review code changes directly. For a campaign page, begin with the offer and the required visitor action. The editor can help produce the design, but an attractive local preview still needs hosting and a real enquiry destination.

This guide covers Cursor’s editor workflow and a remote Pageree connection. The setup is based on documentation reviewed on September 15, 2026; it is not a claim of hands-on testing across Cursor accounts. Confirm the connection in your installed client before treating it as a publishing path.

Add a project-level MCP connection

Cursor documents project configuration in .cursor/mcp.json and user configuration in ~/.cursor/mcp.json. For a project-specific connection, merge the following entry into the project file:

{
  "mcpServers": {
    "pageree": {
      "url": "https://mcp.pageree.com/"
    }
  }
}

Open Cursor’s MCP management interface, enable the server, and complete OAuth when prompted. The exact controls can change between releases. Follow Cursor’s official MCP documentation for the current interface and authentication behavior. Keep existing server entries rather than replacing the whole configuration.

Ask Agent to read your Pageree account and list pages. If it can describe MCP but cannot return a tool result, check the server status, authentication, and whether the tools are enabled for the current conversation. Pageree’s address ends at the root slash; the connection guide maintains that detail.

Keep source assets separate from published assets

An editor preview can load ./photos/team.jpg from your computer. The same path will not work in a Pageree page, which stores a single HTML document. Ask Cursor to upload authorized images through Pageree’s asset workflow and use the returned hosted URLs. Inline the page’s CSS and JavaScript; avoid a dependency on a running development server.

This is also the right point to inspect a starter project. If it contains unused routing, login screens, or a database scaffold, decide whether the campaign actually needs those features. A focused enquiry page rarely needs an application shell around it.

Build an original service page

For an illustrative example, consider a founder offering a website content review to local businesses. Adapt the request to your real service:

Create a landing page for my website content review service in this project.
Audience: owners of local service businesses with confusing or outdated web copy.
Offer: review the core pages and deliver a prioritized list of content changes.
Primary action: request information about the review.
Use brief.md and only the authorized assets provided. Ask for missing proof,
pricing, service boundaries, business name, and destination email.
Build one complete HTML document for Pageree, with inline CSS and JavaScript.
Use its current page, asset, form, privacy, and publishing instructions.
Form fields: name, email, business website, and the main content problem.
Ask me to choose the slug. Save a private preview and persist the page ID.
Do not publish until I review it.

Read the diff before opening the preview. Watch for unrelated file changes, invented testimonials, and placeholder links. A complete consultant template can help you judge whether the offer has enough detail.

Verify behavior outside the editor

Open the actual private preview, including a narrow mobile view. Check the headline, image crop, form labels, keyboard focus, and both success and error messages. If the page was built from a component framework, confirm that the exported result still works without the development environment.

After you approve publication, inspect the public URL. Send a clearly marked test enquiry using an address you control and confirm arrival at the configured destination. A browser success message by itself does not verify delivery. Use the broken-form guide if the request is accepted but no notification arrives.

Maintain one campaign identity

When you return to the project, ask Cursor to read the saved page identity and check for an existing draft. Retrieve the current stored source before replacing it, especially if another assistant has edited the page. Keep unrelated sections, field names, and delivery settings stable unless the requested change requires them.

Save the revision as a new draft on the same page ID, then review and publish. The live-update guide explains how this preserves the campaign URL while keeping changes reviewable.