The Claude Code plugin isn't a bespoke integration — underneath it, HelpBento runs a standard, spec-compliant MCP (Model Context Protocol) server. If you're connecting from Claude Code, the setup steps live in the Claude Code Plugin category; this article covers the server itself, which isn't tied to any one client.
The server
HelpBento's MCP server speaks streamable HTTP (not SSE or stdio) at a single endpoint: https://api.helpbento.com/mcp. It's built on the standard MCP SDK, with no HelpBento-specific protocol quirks — any spec-compliant MCP client that can speak streamable HTTP can, in principle, talk to it.
Authentication: OAuth 2.1, dynamic client registration
Authentication runs over standard MCP OAuth — the same origin serves as both the OAuth authorization server and the MCP resource server. Client registration is dynamic rather than restricted to a fixed allowlist, and every connection completes the same authorization-code exchange before receiving an access token, regardless of which client initiated it.
The whole connection is scoped to a single OAuth scope, described to you plainly on the consent screen: reading your categories and knowledge bases, and creating draft articles. See What the Claude Code plugin can and can't do (permissions & safety) in the Claude Code Plugin category for the full detail on what that scope does and doesn't allow — the permissions model there isn't Claude-specific either, it's how the scope behaves for any client.
The tool surface
The server currently exposes 27 tools — covering knowledge bases, categories, tags, articles, changelog entries, developer-docs versions, API references, image uploads, and content-gap/symbol search. Every article-writing tool in that set lands as a draft, never a publish.