Manage your servers directly from Goose, Block's open-source AI agent. One click installs the ManageLM MCP extension: no editing YAML, no terminal commands.
Click the Add to Goose button above. Goose will open and ask you to confirm enabling the ManageLM extension. That's it. You're done.
Click Add to Goose above (make sure Goose Desktop is installed and running)
Confirm the ManageLM extension when Goose prompts you
Start a session. The ManageLM tools appear in Goose's tool list automatically.
First tool call opens your browser for OAuth login: approve, and Goose is connected
Self-hosted users: The one-click button points at app.managelm.com. For your own portal, use the manual config below and replace the URL.
If the deeplink doesn't work, or you're on a self-hosted portal, add the extension manually via the Goose CLI or by editing the config file.
goose configure
Choose Add Extension → Remote Extension (Streaming HTTP), then enter:
managelmhttps://app.managelm.com/mcp300 (seconds, default is fine)Edit ~/.config/goose/config.yaml and add:
extensions: managelm: type: streamable_http enabled: true name: ManageLM uri: https://app.managelm.com/mcp timeout: 300
Once connected, Goose can:
"all"Goose's autonomous-agent loop pairs naturally with ManageLM: ask it to "audit all production servers and remediate any high-severity findings" and it will plan, execute, and verify the work across your fleet.
ManageLM uses OAuth 2.0 with PKCE. The first tool call triggers a browser authorization flow. Approve access once and tokens refresh automatically.
No account yet? Create one, free for up to 10 agents.
Safari on macOS: Safari's Intelligent Tracking Prevention blocks the OAuth redirect back to Goose's loopback callback (http://127.0.0.1:*). Use Chrome or Firefox as your default browser for the sign-in step, then switch back to Safari after. You only need to do this once per auth session; tokens refresh automatically afterward.
Make sure Goose Desktop is installed and the deeplink handler is registered. On first install, open Goose once so the OS registers the goose:// protocol, then retry. If it still fails, use the manual config.
Open Settings → Extensions in Goose and toggle managelm on. If the connection fails, check that https://app.managelm.com/mcp is reachable from your machine.
Open your ManageLM portal, go to Settings > MCP Credentials, and make sure MCP is enabled for your account.
Long-running tasks (security audits, fleet-wide installs) can take more than the default 300-second timeout. Increase timeout in config.yaml if needed.