Connect Context7 to OpenCode
Give OpenCode governed access to Context7’s 2 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Context7 to OpenCode in four steps
Admins approve the server once. Everyone in OpenCode then gets it through the same governed connection.
- 1
Approve Context7 in Runlayer
Add Context7 from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect OpenCode to Runlayer
Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches Context7’s 2 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
OpenCode setup guide - 3
Sign in to Context7
Sign in the way Context7 requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Context7 from OpenCode
Context7’s approved tools appear in OpenCode. Every call is checked against policy and recorded.
Tools
2 Context7 tools in OpenCode
Runlayer policy decides which of these OpenCode users can call. 2 read data only.
Query docs
Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework.
Resolve library ID
Resolves a package/product name to a Context7-compatible library ID and returns matching libraries.
Control
What Runlayer can see and stop in OpenCode
Some controls apply to every client at the gateway. Others depend on what OpenCode exposes to Runlayer.
Gateway policy (available)
Every Context7 call from OpenCode passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, OpenCode as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.
Frequently asked questions
Connect more