Connect Devin to Goose
Give Goose governed access to Devin’s 24 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Devin to Goose in four steps
Admins approve the server once. Everyone in Goose 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 Goose to Runlayer
Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Devin’s 24 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose 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 Goose
Devin’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
24 Devin tools in Goose
Runlayer policy decides which of these Goose 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 Goose
Some controls apply to every client at the gateway. Others depend on what Goose exposes to Runlayer.
Gateway policy (available)
Every Devin call from Goose passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Goose as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Goose runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Goose’s model sees it.
Redact output in place (not available)
Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.
Frequently asked questions
Connect more