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