Bring Docsy into Claude.

Two clients, two configuration paths

The same Docsy Streamable HTTP MCP endpoint can be used through more than one Claude product. A custom remote connector created through the Claude account is managed in the connectors interface; a direct MCP entry in Claude Code can be installed from the command line. These paths have different settings and should not be mixed with a local stdio extension.

Use https://docsy.remcp.site/mcp as the remote MCP URL for Docsy. The endpoint requires authorization. Do not paste a Docsy password or OAuth token into a public repository, a prompt, or a configuration example. The supported client should guide you through authorization.

Claude web, Cowork or Desktop

For a personal account, Anthropic currently documents Customize → Connectors → Add custom connector. Enter a clear connector name and the remote MCP URL, continue through authentication discovery, and select the sign-in behavior that matches an OAuth-protected server. Sign in when prompted and review the access request.

Claude custom remote connectors are connected from Anthropic's cloud, even when you use the Desktop interface. A publicly reachable HTTPS URL is therefore important. Teams and Enterprise organizations may reserve connector creation for administrators or people with appropriate roles, while other members connect to an already configured integration.

After adding the connector, enable it for the relevant conversation from the Connectors controls. If Claude does not invoke it, first check that it is enabled and authenticated, rather than assuming the server has no documentation.

• Open Customize → Connectors and add a custom remote connector if permitted.
• Use https://docsy.remcp.site/mcp and complete Docsy OAuth.
• Enable Docsy in the conversation's connector controls.
• Ask Claude to resolve a documentation library, then check the original source URL.

Claude Code via HTTP

Claude Code provides a command-line path for connecting an existing remote HTTP MCP server. The following command registers Docsy under the name 'docsy' in the default local project scope. Use --scope user if you need it across projects, or --scope project if you deliberately want a shareable project configuration.

After adding the entry, inspect it with claude mcp list or claude mcp get docsy, then use /mcp in an interactive Claude Code session to review its connection and complete OAuth. A successful 'Added' message means the configuration was saved; it does not by itself prove the remote server is authenticated.

claude mcp add --transport http docsy https://docsy.remcp.site/mcp
claude mcp list
claude mcp get docsy
# In an interactive Claude Code session, run /mcp to sign in and inspect status

An alternative: the community plugin

Docsy also provides a community Claude Code plugin through the getremcp/docsy-plugin repository. That package can include more than a single MCP entry, so review its contents and release notes before installing. Its existence does not mean it is an official Anthropic directory listing.

Choose one installation method to avoid confusing duplicate server names. The remote MCP command above is the clearest starting point when you only need Docsy's hosted documentation tools; the community plugin is a separate distribution option.

If something fails

A 401 to an unauthenticated HTTP request is consistent with the server's OAuth requirement. If Claude Code reports Needs authentication, complete sign-in from /mcp rather than bypassing protection. If Claude Desktop can reach the internet but the connector fails, confirm that you used the remote connectors interface—not a local stdio configuration meant for an executable running on your machine.

If a source result looks inconsistent with the requested package version, inspect the library ID, list available versions and rerun the focused query. This separates setup issues from documentation selection issues.