Manage your servers directly from Cursor while you code. One click installs the ManageLM MCP server — ask Cursor to check production logs, restart services, or run a security audit without leaving your editor.
Click the Add to Cursor button above. Cursor will open and ask you to confirm adding the ManageLM MCP server. That's it — you're done.
Click Add to Cursor above (make sure Cursor is installed and running)
Confirm the MCP server in Cursor when prompted, then click Install
Open the agent panel (Cmd/Ctrl + L). The ManageLM tools appear in the tool list automatically.
First tool call opens your browser for OAuth login — approve, and Cursor 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 MCP server manually:
Edit ~/.cursor/mcp.json:
{
"mcpServers": {
"managelm": {
"url": "https://app.managelm.com/mcp"
}
}
}
Create .cursor/mcp.json in your project root with the same JSON. Useful when only certain projects should have ManageLM access.
Reload after editing: Open Cursor Settings → MCP and toggle managelm off and on, or restart Cursor, to pick up changes.
Once connected, Cursor's agent can:
"all"Cursor pairs especially well for code → deploy → verify loops — ship a config change, then immediately ask Cursor to apply it across your fleet and tail the relevant logs to confirm.
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 Cursor'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 Cursor is installed and the deeplink handler is registered. On first install, open Cursor once so the OS registers the cursor:// protocol, then retry. If it still fails, use the manual config.
The MCP server isn't reachable or hasn't been authenticated yet. Try a tool call from the chat panel — the OAuth flow will start. If you're on a self-hosted portal, verify the URL is reachable from your machine.
Open your ManageLM portal, go to Settings > MCP Credentials, and make sure MCP is enabled for your account.
Make sure managelm is enabled in Settings → MCP. If it is and tools still don't show, restart Cursor.