What it does
The server connects AI assistants such as Claude to a website's pages, including creation, updates, publishing, duplication, layouts, HEEx templates and SEO metadata. It also covers blog posts and their listing and post-card designs, reusable components with editable props, forms and form submissions, and media uploads and folders. Analytics tools return visitor statistics, top pages, referrers and device, browser and country breakdowns. Redirects, layouts, error pages, global code and versioning are also included.
It suits people who already run sites on this platform and want an assistant to handle routine content, form, media or traffic-review tasks through a single connection, rather than working in the dashboard for each step.
The server uses Streamable HTTP. Clients that support OAuth 2.1 can discover the sign-in flow automatically and register without manual app setup. Clients without OAuth support use a personal API key, created after signing in to the service under its settings.
Limitations and requirements
Requires an account on the BrightSite service. Clients without OAuth support need a personal API key, created in the account settings under MCP Keys.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
BrightSite
Manage BrightSite websites: pages, blog posts, components, forms, media, and analytics.
v1.0.0As shown on registry.modelcontextprotocol.io when we last read it