Skip to main content
Context7 integrates with DeepSeek Harness through the official @upstash/context7-deepseek-harness plugin. It registers Context7’s documentation tools natively through the harness tool service and adds system-prompt guidance so library-specific questions invoke them automatically.

​
Installation

Install the bundle into a DeepSeek Harness profile and store a Context7 API key in the Harness credential provider:
Pass another profile name instead of headless when needed. Without an existing Context7 login, setup starts the device authorization flow and creates an API key. To use anonymous Context7 limits without configuring a key, install the bundle directly:
Verify the composed configuration and start the profile:
Remove it with dsh plugin --profile headless remove @upstash/context7-deepseek-harness.

​
Authentication

The plugin resolves CONTEXT7_API_KEY through DeepSeek Harness’s credential provider before every request. The setup command stores it in $DSH_HOME/.credentials.yaml, which defaults to ~/.dsh/.credentials.yaml. Credential changes apply without reloading the plugin. The launching environment remains supported:
For manual credential-file setup, edit the flat YAML mapping and apply owner-only permissions:
Never put API keys in cordis.yml or cordis.patch.yml; composed configuration can be printed and shared during debugging.

​
What it adds

resolve-library-id

Finds Context7-compatible library IDs and available versions for a package or product.

query-docs

Fetches current documentation and code examples for a selected library ID.

​
Usage

Ask a documentation question in a DeepSeek Harness session:
The model resolves the relevant Context7 library ID and then queries its documentation.