Connect Context7 to Raycast
Give Raycast governed access to Context7’s 2 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Context7 to Raycast in four steps
Admins approve the server once. Everyone in Raycast 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 Raycast to Runlayer
Users add the Runlayer Plugin to Raycast by following Runlayer’s setup guide. Raycast reaches Context7’s 2 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Raycast 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 Raycast
Context7’s approved tools appear in Raycast. Every call is checked against policy and recorded.
Tools
2 Context7 tools in Raycast
Runlayer policy decides which of these Raycast 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 Raycast
Some controls apply to every client at the gateway. Others depend on what Raycast exposes to Runlayer.
Gateway policy (available)
Every Context7 call from Raycast passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Raycast as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Raycast yet, so control happens at the gateway.
Frequently asked questions
Connect more