BrightSite

io.github.BrightSiteHQPublished by GitHub account BrightSiteHQv1.0.0Updated Oct 28, 2026

Manage BrightSite websites: pages, blog posts, components, forms, media, and analytics.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & CommerceMedia & Design

Overview

AI-generated overview

Remote BrightSite MCP server that lets an assistant manage a BrightSite website's pages, blog, components, forms, media and analytics.

What you can do
  • Create, update, publish and duplicate pages, including layouts, templates and SEO metadata
  • Manage blog posts, listing and post-card designs, blog settings and templates
  • Build reusable components with editable props, plus redirects, layouts, error pages and global code
  • Create forms and view their submissions
  • Upload media files and organize folders
  • Read analytics: visitor stats, top pages, referrers and device, browser and country breakdowns
When to use it
Useful when you run a site on BrightSite and want an assistant to draft or edit pages and blog content, adjust components and forms, upload media, or pull traffic analytics without using the dashboard by hand.
Requirements
A BrightSite account and a site on onbrightsite.com. Connects to the remote Streamable HTTP endpoint; OAuth 2.1 with dynamic client registration is negotiated automatically by capable clients, otherwise a personal API key from Settings → MCP Keys is sent as an Authorization Bearer header. Network access required.
Before you install
The server can change live site content: pages can be published, duplicated and updated, and forms, media, redirects and global code can be modified. Access is granted through an OAuth login or a personal API key, so treat that key as a secret and revoke it if leaked. Analytics and site data are read from and written to BrightSite's hosted service.

Installation

In SourceWeft

  1. Open BrightSite in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.BrightSiteHQ%2Fbrightsite/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "brightsite": {
      "type": "http",
      "url": "https://onbrightsite.com/api/mcp"
    }
  }
}

README

BrightSite MCP Server

The official Model Context Protocol server for BrightSite — connect AI assistants like Claude to manage your websites, pages, blog posts, components, forms, media, and analytics.

Endpoint

https://onbrightsite.com/api/mcp

Transport: Streamable HTTP.

Authentication

The server supports two authentication methods. Most modern MCP clients will negotiate OAuth automatically; clients that don't can fall back to a Bearer token.

OAuth 2.1 (recommended)

OAuth-capable clients (Claude.ai, ChatGPT, Claude Desktop with OAuth, etc.) discover the auth flow automatically via /.well-known/oauth-protected-resource. Dynamic Client Registration (RFC 7591) is supported — no manual app setup needed.

Bearer token

For clients that don't support OAuth, generate a personal API key:

  1. Sign in at onbrightsite.com
  2. Go to Settings → MCP Keys
  3. Create a new key (format: bs_...)
  4. Configure your client with:
json
{  "mcpServers": {    "brightsite": {      "url": "https://onbrightsite.com/api/mcp",      "headers": {        "Authorization": "Bearer YOUR_API_KEY"      }    }  }}

Capabilities

  • Pages — create, update, publish, duplicate; manage layouts, HEEx templates, and SEO metadata
  • Blog — posts, listing/post-card designs, blog settings, templates
  • Components — reusable UI blocks with editable props
  • Forms — create forms, view submissions
  • Media — upload files, manage folders
  • Analytics — visitor stats, top pages, referrers, device/browser/country breakdowns
  • Redirects, layouts, error pages, global code, versioning

Registry

This server is published to the MCP Registry as io.github.brightsitehq/brightsite. The canonical metadata is in server.json.

Links

Source: README.md at commit fabedcb

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.