Context7

How do you get Context7 results for the right version?

Start with the installed version from your package manifest or lockfile. Use resolve-library-id to identify the right library and available versions, then ask query-docs about one API or behavior.

• Check the owner and repository when two libraries share a name.
• If the supported list includes your version, use the versioned library ID and compare the returned example with the official documentation before editing.

Resolve the library before using the example

A useful documentation query begins with the correct library identity. Similar package names, framework adapters and version changes can lead to different APIs. Library resolution and a focused query narrow the material before an agent applies an example to the codebase.

Choose the interface for the workflow

The repository offers a CLI-plus-skills route as well as an MCP route. CLI provides command-oriented integration; MCP exposes documentation tools through a compatible client. The two have separate setup paths and do not require identical local configuration.

Connection requirements and rate limits

Runtime and access requirements belong to the route being installed. A hosted MCP connection and a locally executed CLI have different setup boundaries. Current client, authentication and runtime instructions are more reliable than requirements copied from an older package tutorial.

Context7 recommends a free API key for higher rate limits. For a hosted connection, follow your client’s setup instructions and keep the key in its private configuration.

Apply documentation to the actual project

Returned material still needs to match the installed package, requested API and framework. An example can clarify an implementation, but it does not check the application’s data, configuration or behavior. Those outcomes require review and execution of the resulting code.

When changing a form after a dependency upgrade, first check the exact API against the version in the lockfile. After applying the change, use Playwright MCP to check a successful submission and a validation error in the running app.

A few more details

Sources & maker notes

This guide is based on the cited documentation and maker sources. vibeforthat has not run an independent installation or end-to-end product test for this article.

• Context7 version lookup example
• github.com