Loading Docsy
Skip to content
LibrariesAtlasHow it worksDocsNotesConnectGitHub →
Get started →
Get started →
Loading page

A working index of primary documentation.
Library, release, reference — always traceable to the source.

ExploreLibrariesKnowledge atlasDashboardDocumentationConnect via MCP
ResourcesMCP plugin source ↗SDK & CLI source ↗Official MCP Registry ↗Glama health report ↗Quick start & APIField NotesSupportPrivacy PolicyTerms of ServiceMIT License →
© 2026 Docsy. Plugin built in the open.Independent documentation index. Open-source MCP integration.
DOCSY / CONNECT / MCP

One source.
Every workflow.

Native setup examples for popular coding agents and editors. Choose your client, add the hosted MCP endpoint, authorize your Docsy account and verify a documentation source link.

Read the MCP handbook →Manage connections →
INSTALL / CLIENT DIRECTORY

Bring Docsy to your agent.

Choose your client for a native installation example. Every connection requires Docsy OAuth authorization.

13 CLIENTS
SETUP / CLI

Claude Code

Register Docsy as a remote HTTP MCP server.

Client documentation →
Terminal · user or project scopeSHELL
claude mcp add --transport http docsy https://docsy.remcp.site/mcp
02 / AUTHORIZE & VERIFY

In Claude Code, run /mcp to sign in; then check claude mcp list.

Test the integration with a sourced documentation query +

Use Docsy to find the official React useEffect cleanup guidance, identify the resolved library and show the original source URL.

https://docsy.remcp.site/mcp
Manage OAuth connections →

Client software, features and authentication flows change independently of Docsy. Configuration is not proof of a live authorized connection. Community integration is not an official vendor endorsement.