Connect Docsy to ChatGPT.

Before adding a server

Docsy is a source-linked technical documentation index. Its hosted MCP endpoint is https://docsy.remcp.site/mcp. It uses Streamable HTTP and asks the MCP client to sign you in using Docsy OAuth; a raw browser request that has no credentials may receive HTTP 401. That response alone does not mean the service is down.

A public MCP Registry record, a hosted MCP endpoint, and a ChatGPT directory listing are three different things. Registration in the MCP Registry does not imply that a third-party plugin is published or enabled in every ChatGPT workspace. Use a vetted directory entry if it is available to your account, or add a custom MCP server if your account and workspace permit it.

OpenAI's current guidance describes custom server connections under Plugins, subject to your workspace permissions. Business administrators or owners and authorized Enterprise/Edu users may have different creation and publication rights. Plan entitlements and the exact interface can change; check the linked official instructions rather than assuming every ChatGPT account exposes the same controls.

Connect through Plugins

Open ChatGPT on the web, go to Plugins, choose the plus button and select Add custom MCP server if that option is available. Give the connection a recognizable name such as Docsy, enter the public HTTPS server URL, and configure authentication using the connection's OAuth flow.

Read the risk notice and the list of tools before proceeding. Choose Create as a plugin to inspect the tools detected by ChatGPT. When redirected to Docsy, sign in to your account and approve only the access that you expect. Admins should review which members may use a shared workspace plugin before publishing it.

Custom MCP server creation is governed by ChatGPT plan and workspace permissions. Business workspace admins/owners and authorized Enterprise/Edu members can create eligible connections; Pro read/fetch access may differ from full MCP capabilities. See the current official availability and permissions guide before continuing.

If you do not see Add custom MCP server, the relevant workspace permission or plan may be unavailable. Do not change unrelated account security settings just to make a tutorial match your screen. Consult the latest official OpenAI permissions guide and consider the existing public Docsy plugin where supported.

• Open ChatGPT on the web and check Plugins for Add custom MCP server.
• Enter https://docsy.remcp.site/mcp as the public HTTPS MCP URL.
• Complete Docsy OAuth when the client requests authorization.
• Inspect the discovered read-only documentation tools and permissions.
• Use the connected plugin for a narrow documentation question, then inspect the source URLs in the result.

Run one verifiable query

Ask: 'Find the official React useEffect cleanup guidance and include the source URL.' A useful result should identify the library and point to official source material. If you are implementing against a particular React release, name the release in the request and check that the selected indexed edition matches it.

Try a follow-up: 'Which Next.js 16.4.2 documentation describes revalidateTag?' This is a good test of version-specific retrieval. The purpose is not to trust an AI summary over the documentation, but to shorten the path to the right reference.

Troubleshoot the connection

A missing server-creation option is a ChatGPT plan or workspace-permission question. A tool scan that fails before login may indicate a server URL or MCP discovery problem. A sign-in screen that fails to return to ChatGPT suggests an OAuth callback or consent issue. Capture the error message, approximate time and client name without publishing tokens or account identifiers.

A 401 on a direct unauthenticated HTTP request is compatible with an OAuth-protected server. It is not proof that your authenticated plugin session is working, either. Verify within ChatGPT that tool discovery completes, OAuth succeeds, and a source-linked query returns results. Manage and revoke the OAuth connection from your Docsy account dashboard when you no longer need it.

Always review external content returned by tools. A read-only description does not turn arbitrary third-party documentation into trusted instructions for your agent.