Skip to main content
Context7 integrates with OpenCode to provide current library documentation instead of relying on training data. Get accurate, up-to-date code examples directly in your coding sessions.
For more details on MCP server configuration in OpenCode, see the OpenCode MCP documentation.

​
Installation

Run the setup command to configure Context7 for OpenCode:
Authenticates via OAuth, generates an API key, and installs the appropriate skill. You can choose between CLI or MCP mode. You can also install Context7 as an OpenCode plugin. It bundles the MCP server with a skill:
Restart OpenCode after installing, then authenticate the plugin:
Complete the OAuth flow in your browser to use your account’s rate limits. If you skip this command, the browser opens automatically on the first lookup. For manual MCP installation or other configuration options, see All MCP Clients.

​
Plugin

Install the plugin from your project directory:
The plugin is an alternative to ctx7 setup that configures OpenCode in one command. It adds two things:

MCP Server

The tools for fetching documentation (context7_resolve-library-id, context7_query-docs)

Skills

context7-mcp auto-triggers documentation lookups when you ask about libraries
You can also add the plugin to your config by hand:
opencode.json

​
API Key

The plugin uses OAuth by default and needs no configuration. To use an API key instead, for example on a headless machine, export it before launching OpenCode:
The plugin picks up CONTEXT7_API_KEY automatically and sends it as an Authorization header. You can also pass it through the plugin options:
opencode.json
Create or manage API keys in the Context7 dashboard. Everything the plugin adds is additive, and your own configuration always wins. If your opencode.json already defines an MCP server named context7, the plugin leaves it alone. It is also safe to run both ctx7 setup and the plugin, since OpenCode loads the context7-mcp skill once.

​
Using Context7

With ctx7 setup or the plugin, a skill is installed that triggers automatically when you ask about libraries. You can also invoke it explicitly:
If you know the library ID, use it directly to skip resolution:
You can also add instructions to your AGENTS.md file:
AGENTS.md

​
Tips

  • Be specific about what you’re trying to do, not just which library
  • Mention versions when they matter
  • If the first result isn’t right, ask for a different part of the docs
You can place your opencode.json in your project directory to have project-specific configurations. This is useful when:
  • Different projects need different API keys
  • You want to share the config with your team via version control
  • A project requires specific Context7 settings