English Français العربية

BrightSite

Official registry Marketing and sales

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

Source code Documentation

What can you do with BrightSite?

  • 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

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http brightsite 'https://onbrightsite.com/api/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "brightsite": {
            "type": "http",
            "url": "https://onbrightsite.com/api/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. BrightSite MCP Server
  2. Endpoint
  3. Authentication
  4. Capabilities
  5. Registry
  6. Links

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-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:
{
  "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.

Frequently asked questions

What is BrightSite?

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

How do I install BrightSite?

It runs as a remote server. In Claude Code: claude mcp add --transport http brightsite 'https://onbrightsite.com/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does BrightSite need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is BrightSite open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains BrightSite?

It is published by BrightSiteHQ. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.