Read the docs. Then touch the code.

Two services. Different responsibilities.

Good code is not produced by recalling an API name alone. You have to know which version a project actually depends on, what the original documentation says, and whether the change works in that specific repository. Docsy and ReMCP address different parts of that sequence.

Docsy is a read-only documentation retrieval service. Its five MCP tools can resolve a library, list indexed versions, ask a version-scoped question, search public documentation and fetch an indexed result. It returns publisher links so an assistant can check where the guidance came from.

ReMCP provides authorized remote access to paired Windows, macOS and Linux computers. Subject to device capabilities and permissions, an AI client can read project files, edit code, run commands, inspect running applications and verify results. Docsy does not run terminal commands; ReMCP does not replace the upstream documentation.

Why source-linked coding matters

An assistant can give an answer that looks correct but belongs to a different release. Before changing a project, inspect the package manifest and lockfile, identify the actual library version and use Docsy to retrieve the corresponding API reference. Then read the original source link; an indexed excerpt may be partial or incomplete.

A source link is a trace of where the recommendation came from, not a guarantee of correctness. Current documentation may not cover every package version or application-specific constraint. The project's tests, types and actual runtime behavior remain essential.

• Identify the repository's framework, lockfile and installed versions.
• Resolve the library and check which documentation versions Docsy has indexed.
• Ask for the exact API behavior needed, then follow the original documentation URL.
• Keep external documentation text separate from trusted user instructions.

Turn a reference into a verified change

With ReMCP, the assistant can inspect relevant source files on the authorized development machine, make a small and reversible patch, then run the project's own type checker, tests and build. For visual changes it can inspect a browser or a screenshot when a graphical session is available.

A healthy workflow does not jump from receiving a Docsy answer straight to deploying. It checks the diff, preserves unrelated work, reports failures, and applies corrections locally before a reviewed release. High-impact changes still require appropriate authorization.

• Inspect files and project conventions before editing.
• Make the smallest supported change rather than reformatting unrelated code.
• Run the project's native checks and inspect their exit codes.
• Compare the result to the documentation and user requirements.
• Publish only after the required verification and review.

Connect ReMCP and Docsy

Connect the two services independently in an MCP-compatible AI client. ReMCP uses https://remcp.site/mcp and requires an authorized ReMCP account and paired device. Docsy's canonical remote endpoint is https://docsy.remcp.site/mcp/registry and its MCP connection uses Docsy OAuth.

The value of using both is a repeatable evidence trail: the relevant documentation, the actual file change, and the result of testing on a machine you control. No retrieval service or AI assistant can promise perfect code in every situation. Sources and verification are how you catch mistakes.