Site Context

⚡ Built-in — Platform Built-in

Design context per project — colors, fonts, style notes. Supports multiple sections (e.g. "frontend" and "admin") for projects with different visual styles. Default section is included in get_project_status. Use set-context with a section parameter to store separate design contexts.

⚡ Built-in — No Setup Required This integration is built into the WebsitePublisher platform. All endpoints are available immediately — no API key needed.

Try it with your AI assistant

Once WebsitePublisher is connected to your AI assistant, paste one of these into the chat. Replace the parts in [brackets] with your own details.

ChatGPT Claude Other assistants

@WebsitePublisher remember my brand style for every page: colors [your colors], fonts [your fonts] and a [modern, minimal] look

@WebsitePublisher give my admin pages their own calmer style, separate from the public site

With WebsitePublisher, remember my brand style for every page: colors [your colors], fonts [your fonts] and a [modern, minimal] look

With WebsitePublisher, give my admin pages their own calmer style, separate from the public site

With WebsitePublisher, remember my brand style for every page: colors [your colors], fonts [your fonts] and a [modern, minimal] look

With WebsitePublisher, give my admin pages their own calmer style, separate from the public site

Endpoints (4)

POST set-context

Set or update design context for a project section. Uses deep merge — only provided fields are overwritten, existing fields are preserved. Use the section parameter to store separate contexts for frontend, admin, email-templates, etc. Without section, writes to "default".

Field	Type	Required	Description
`section`	string	No	Section name for this context, e.g. "frontend", "admin", "email". Lowercase, alphanumeric + hyphens. Defaults to "default". Max 10 sections per project.
`color_palette`	array	No	Color palette object. Keys: primary, secondary, accent, background, text. Values: hex color strings (e.g. "#2D5A3D").
`fonts`	array	No	Font families object. Keys: heading, body. Values: font family name strings (e.g. "Playfair Display").
`style_notes`	string	No	Free-form style description for AI context, e.g. "Modern minimalist, lots of whitespace, rounded corners, soft shadows".
`locale`	string	No	Primary content language (ISO 639-1), e.g. "nl", "en", "de".

GET get-context

Get the design context for a project. Without section parameter, returns "default" section. Use section="all" to retrieve all sections as a keyed object. Note: the default section is also included in the get_project_status response.

Field	Type	Required	Description
`section`	string	No	Section name to retrieve, e.g. "frontend", "admin". Use "all" to get all sections. Defaults to "default".

GET list-sections

List all section names that have design context stored for this project. Returns an array like ["default", "frontend", "admin"].

No input parameters required.

POST delete-context

Delete design context for a project. With section parameter, deletes only that section. Without section, deletes ALL sections for the project.

Field	Type	Required	Description
`section`	string	No	Section to delete. If omitted, ALL sections are deleted.

MCP Tool Names

When using this integration through an AI assistant (Claude, ChatGPT, Cursor, etc.), the endpoints are available as MCP tools:

Endpoint	MCP Tool Name
set-context	`site_context_set_context`
get-context	`site_context_get_context`
list-sections	`site_context_list_sections`
delete-context	`site_context_delete_context`

← Back to all integrations