Plugs Claude or other MCP clients directly into your BrightSite account to manage websites through conversation. You get full CRUD on pages, blog posts, and reusable components, plus form and media management, analytics queries, and control over redirects and layouts. Authentication is OAuth 2.1 with dynamic client registration, or you can fall back to a bearer token if your client doesn't negotiate flows automatically. Useful when you're iterating on content or structure and want to skip the dashboard, or when you're building workflows that need to pull analytics or publish updates programmatically without leaving your chat interface.
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.
https://onbrightsite.com/api/mcp
Transport: Streamable HTTP.
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.
For clients that don't support OAuth, generate a personal API key:
bs_...){
"mcpServers": {
"brightsite": {
"url": "https://onbrightsite.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
This server is published to the MCP Registry as io.github.brightsitehq/brightsite. The canonical metadata is in server.json.
io.github.infoinlet-marketplace/mcp-observability
betterdb-inc/monitor
com.mcparmory/datadog
thotischner/observability-mcp
io.github.tantiope/datadog-mcp
io.github.us-all/datadog