Clean Pro MCP checking…

Build Clean Pro pages by describing them.

This server teaches Claude, Claude Code, Codex and Cursor everything about the Clean Pro theme: every module, its exact insert path, ready-made recipes, style presets and design rules. Pair it with HubSpot's connector and describe the page you want.

https://mcp.clean.pro/mcp

Why you need it

HubSpot's own AI connector can create and edit pages, but it cannot see the modules inside a theme. Ask it for a Clean Pro FAQ or a card grid and it either builds a custom template that ignores your theme settings, or gives up. This server fills that gap. It is read-only: it never touches your portal and stores nothing.

Finds the right module

Describe what you need in plain words and get the exact module and insert path, with the tie-break rules a Clean Pro expert would apply.

Recipes and presets

Ready-to-send configurations for the most used modules, plus style presets such as a light band, a dark band or a tight section, so pages look designed rather than default.

Checks before it sends

Every payload is validated against the real module schema before it goes to HubSpot, so you get a working section instead of a silent failure.

Set it up

Two connections: this server for Clean Pro knowledge, and HubSpot for the actual page writes. Pick your tool.

Add the Clean Pro connector

In Claude, open Settings → Connectors → Add custom connector. Name it Clean Pro, paste the URL below, leave authentication off. Custom connectors are available on paid Claude plans.

https://mcp.clean.pro/mcp

Add the HubSpot connector

In the same Connectors list, connect HubSpot and approve the full permission list when it asks. A reduced permission set causes internal errors on page reads. HubSpot's guide.

Start a chat and paste the prompt below

Turn both connectors on for the chat, fill in your portal ID and your brief, and send.

Add the Clean Pro server

claude mcp add --transport http clean-pro https://mcp.clean.pro/mcp

Connect HubSpot

Claude Code uses the connectors from your claude.ai account. Add HubSpot there (Settings → Connectors), or run /mcp inside Claude Code to check what is connected.

Paste the prompt below

Fill in your portal ID and your brief.

Add the Clean Pro server to ~/.codex/config.toml

[mcp_servers.clean-pro]
url = "https://mcp.clean.pro/mcp"

Newer Codex builds also accept codex mcp add clean-pro --url https://mcp.clean.pro/mcp.

Connect HubSpot

Codex needs a HubSpot MCP server for the page writes. Use HubSpot's official MCP from the HubSpot developer docs, added the same way.

Paste the prompt below

Add the Clean Pro server to .cursor/mcp.json

{
  "mcpServers": {
    "clean-pro": { "url": "https://mcp.clean.pro/mcp" }
  }
}

Connect HubSpot

Add HubSpot's official MCP server to the same file for the page writes.

Paste the prompt below

The prompt

Copy this into a new chat, replace the two blanks, and describe the page. It sets the rules that make the difference: use the Clean Pro server for knowledge, HubSpot for writes, validate before sending, draft only.

I build HubSpot website pages with the Clean Pro theme. My portal ID is [PORTAL ID].

Use the Clean Pro MCP for everything about the theme: call find_module or list_modules to choose modules, get_module for the exact insert path and fields, use its recipes and style presets, read design_rules before laying out a page, and run validate_overrides on every payload before you send it. Use the HubSpot connector for the actual page work. Never author a custom HubL template; always create pages from a Clean Pro template. Default to website pages. Send content fields plus at most one style preset per section; leave every other style to the theme. Alternate section bands so the page does not read as one white sheet, and use one dark band for the closing call to action. Do not invent image URLs; leave the theme placeholder and tell me which images you still need. Do not publish anything; build the draft, render it once, and show me.

Here is the page I want:
[DESCRIBE THE PAGE: what it is for, the sections you want, the copy or the key messages, and any links, images or forms you already have]

Things it does well from a short brief:

The server never sees your HubSpot account. Page writes go through HubSpot's own connector under your login, and every page is created as a draft until you publish it yourself.

What the server exposes

Nine read-only tools. Your AI client calls them; you never need to.

find_module, list_modules

Discovery by plain-language need or by browsing the catalog.

get_module, get_recipes, get_presets

The reference for one module: fields, allowed values, ready configurations, band presets.

validate_overrides

Checks a payload against the real schema and reports the exact problem.

design_rules, connector_notes, field_shapes

How to compose a page, how HubSpot's connector really behaves, and exact JSON shapes.