Connect Lucid to Goose
Give Goose governed access to Lucid’s 42 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Lucid to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Lucid in Runlayer
Add Lucid from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Goose to Runlayer
Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Lucid’s 42 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Lucid
Sign in the way Lucid requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Lucid from Goose
Lucid’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
42 Lucid tools in Goose
Runlayer policy decides which of these Goose users can call. 2 read data only.
Create embed
Internal tool for MCP Apps extension only.
Create embed session token
Internal tool for MCP Apps extension only.
Exchange legacy embed session
Internal tool for MCP Apps extension only.
Fetch Lucid document content
Retrieves the structured content of a specific Lucid document by its ID.
Get MCP resource
Reads a resource from this MCP server by URI.
List document thread comments
List comments on a specific collaboration thread of a Lucid document.
List document threads
List collaboration threads on a Lucid document.
Add block
Add a new block (shape) to a Lucid document.
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 Lucid 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