Research competitors with sources
Produce a useful competitor comparison with traceable facts, dates, and explicit uncertainty.
Tools & integrations
Retrieve focused library documentation when version details matter.
Use a documentation integration when the project’s installed package version matters and your agent needs an authoritative API detail. Ask a narrow question about the identified library and version; requesting an entire manual can make context harder to use.
Review the upstream setup for your chosen client and the current requirements for hosted access. Resolve the intended library carefully, especially when multiple packages have similar names. Preserve a source link with any implementation decision the returned documentation informs.
Documentation retrieval does not prove that a suggested change works in your repository. Compare the answer with the lockfile and run the relevant local check after editing. Context7 is optional when the existing project docs or an already available official source answer the question without another integration.
Tool setup checked against official documentation. Pristren has not executed this workflow through this tool.
Upstream manual setup template — replace the placeholder privately
[mcp_servers.context7]
url = "https://mcp.context7.com/mcp"
http_headers = { "Authorization" = "Bearer YOUR_API_KEY" }Command referenceLicense and access: MIT for repository code. Hosted access, quotas, and plan terms must be checked with Context7.
Produce a useful competitor comparison with traceable facts, dates, and explicit uncertainty.
Add one integration because a task needs it, then verify its scope and connection.