Connect Devin to Glean
Give Glean governed access to Devin’s 24 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Devin to Glean in four steps
Admins approve the server once. Everyone in Glean then gets it through the same governed connection.
- 1
Add Devin to Runlayer
Devin isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Glean to Runlayer
Users add the Runlayer Plugin to Glean by following Runlayer’s setup guide. Glean reaches Devin’s 24 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Glean setup guide - 3
Sign in to Devin
Sign in the way Devin requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Devin from Glean
Devin’s approved tools appear in Glean. Every call is checked against policy and recorded.
Tools
24 Devin tools in Glean
Runlayer policy decides which of these Glean users can call.
Ask wiki question
Ask any question about a GitHub repository's codebase and get an AI-powered answer grounded in its DeepWiki.
Automation manage
Manage Devin automations.
Billing tag manage
Manage Devin billing tags (groupings of Devin sessions for usage tracking) with a single action-based tool: list/get/create tags, assign sessions one at a time or in bulk (up to 500 per call, sent in…
Blueprint test
Test a candidate blueprint YAML in an authoring VM: start → run initialize → fix → run initialize again (clean VM) → run maintenance → then persist with update_environment_config.
Campaign manage
Read and publish a bot's campaign: its plan, its append-only readings and its status.
Code scan manage
Manage Devin code scans (sometimes referred to as "security scans" or "Devin Security Swarm").
Find setting
Find a Devin webapp setting and get a deep-link URL to it.
Knowledge manage
Manage Devin knowledge notes and suggestions via a single action-based tool.
Control
What Runlayer can see and stop in Glean
Some controls apply to every client at the gateway. Others depend on what Glean exposes to Runlayer.
Gateway policy (available)
Every Devin call from Glean passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Glean as the client, the tool, and the policy and scanner decisions.
OTLP telemetry (available)
Glean can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Glean yet, so control happens at the gateway.
In Glean
- Runlayer sees Glean activity through OpenTelemetry traces for monitoring only; enforcement happens at the gateway.
Frequently asked questions
Connect more