Connect your editor to the source.

Why use MCP inside the editor?

A coding agent already sees your local repository, but that does not guarantee it knows the public APIs for the versions your application uses. Remote documentation retrieval complements code search: resolve the official library, select the edition and read focused excerpts with traceable URLs.

Cursor officially supports remote MCP servers over Streamable HTTP and permits configuration through its Customize interface or an mcp.json file. The hosted Docsy endpoint is https://docsy.remcp.site/mcp. It uses OAuth; the editor must complete the provider's authentication flow before protected tools can be invoked.

Add Docsy to mcp.json

Open Cursor's MCP settings under Customize, or edit a Cursor MCP configuration file. Use the shape below for a remote HTTP server. In a personal configuration, the usual file is ~/.cursor/mcp.json; a project-specific configuration can be kept at .cursor/mcp.json when appropriate. Avoid committing credentials or user-specific secrets to a team repository.

The URL is a hosted service, not a local command. It does not need npx or a port on your laptop. Cursor documents the mcpServers map with a url entry for HTTP/SSE remote servers. Save the file, return to MCP settings and follow the OAuth prompt if offered.

{
  "mcpServers": {
    "docsy": {
      "url": "https://docsy.remcp.site/mcp"
    }
  }
}

Verify instead of guessing

Confirm that Docsy appears as a connected MCP server in Cursor. If tools are missing or show an error, inspect the connection status and any OAuth prompt. Do not interpret a successful paste of JSON as proof of a working authentication session.

Start with a narrowly scoped request: 'Use Docsy to find the React useEffect cleanup reference and give the original URL.' Then request a specific indexed version. A good result links back to a real page; it does not merely propose code without references.

Docsy also exposes a one-click Cursor deep link from its website. Treat that as a convenience for writing configuration, not a substitute for reviewing the actual URL and permissions in Cursor before signing in.

• Add the remote HTTPS endpoint through Cursor MCP settings or mcp.json.
• Complete Docsy OAuth and verify that tools are available.
• Ask a focused library-and-version question.
• Check the primary source URL and compare the returned API to your project dependency.
• If needed, disconnect the server and revoke the OAuth authorization from Docsy.

Debug common mistakes

A configuration that starts a local command is not equivalent to a remote URL entry. Use url for the hosted HTTP endpoint; reserve command and args for stdio servers that actually launch locally. JSON formatting errors can prevent Cursor from reading the entire configuration, so validate the file if discovery fails.

A 401 outside Cursor on an anonymous request does not imply that Docsy is offline. Within Cursor, distinguish transport errors, OAuth problems and missing documentation. If an older library release is not indexed, choose an available version or use the source link rather than silently accepting information from a different release.

MCP exposes external text to an agent. Treat it as reference material, not as authorization to change your project. Review generated code and execute tests before merging.