Manage BrightSite websites: pages, blog posts, components, forms, media, and analytics.
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. 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…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
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. 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 . Dynamic…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.