Connect Mintlify to Crush
Give Crush governed access to Mintlify’s 35 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Mintlify to Crush in four steps
Admins approve the server once. Everyone in Crush then gets it through the same governed connection.
- 1
Add Mintlify to Runlayer
Mintlify isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Crush to Runlayer
Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches Mintlify’s 35 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Crush setup guide - 3
Sign in to Mintlify
Sign in the way Mintlify requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Mintlify from Crush
Mintlify’s approved tools appear in Crush. Every call is checked against policy and recorded.
Tools
35 Mintlify tools in Crush
Runlayer policy decides which of these Crush users can call.
Agent review settings
Change whether agent edits push directly to the deploy branch (push_to_main) or open a pull request (create_pull_request).
Checkout
Select a deployment and open its editor session in one call.
Create node
Insert a node into the navigation tree under parentId (null = root).
Delete node
Remove a node and its subtree from the navigation tree by nodeId.
Diff
Returns the list of changes between current session and main.
Discard session
End the session without creating a PR.
Edit page
String-replace edit on a page Y.
Execute code
Run TypeScript/JavaScript against the Admin MCP dashboard SDK inside a sandboxed Cloudflare isolate.
Control
What Runlayer can see and stop in Crush
Some controls apply to every client at the gateway. Others depend on what Crush exposes to Runlayer.
Gateway policy (available)
Every Mintlify call from Crush passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Crush as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Crush yet, so control happens at the gateway.
Frequently asked questions
Connect more