MCP Extension Copilot Extension

VS Code Integration

Two ways to use ManageLM in VS Code: a one-click MCP install for native Copilot Chat agent mode, or the ManageLM extension for the dedicated @managelm chat participant.

Install MCP Download Extension MCP install is recommended. The extension provides the @managelm participant if you prefer that style.

Choose Your Integration

Both paths work side by side. Pick what suits your workflow. Most users want the MCP install: it's faster, gets every ManageLM tool automatically, and uses VS Code's native MCP support.

MCP IntegrationVS Code Extension
InstallOne click via deeplinkDownload .vsix + install
Where it shows upCopilot Chat in Agent mode, tools pickerCopilot Chat as @managelm participant
AuthenticationOAuth 2.0 with PKCE (browser flow)API key in VS Code settings
Tool surfaceEvery ManageLM tool and one tool per skill (auto-updates)33 tools modelled on the MCP tools; tasks and scans on one server at a time
UpdatesServer-side: nothing to reinstallRe-install the .vsix when new versions ship
VS Code version1.99+ (April 2025)1.99+
Copilot subscriptionRequired (Agent mode)Required (Chat participant)

Can I have both? Yes. They don't conflict. You can install MCP for general agent-mode use and keep the extension for the @managelm shortcut.

MCP Integration

This is the modern, recommended path. ManageLM exposes a remote MCP server at https://app.managelm.com/mcp. VS Code 1.99+ has native MCP support built into Copilot Chat, no extension needed.

MCP: Install

One-click install

Click the button below. VS Code opens a confirmation dialog with the server pre-filled, click Install.

Install MCP in VS Code

Manual config

If the deeplink doesn't fire, open the Command Palette and run MCP: Open User Configuration, then paste:

mcp.json
{
  "servers": {
    "managelm": {
      "type": "http",
      "url": "https://app.managelm.com/mcp"
    }
  }
}

Self-hosted users: Replace app.managelm.com with your own portal URL.

MCP: Use

Daily usage

  1. Open Copilot Chat (Ctrl/Cmd+Alt+I)

  2. Switch the chat mode to Agent (dropdown at the top of the chat)

  3. Type a request: "list my managelm servers", "check disk usage on web-prod-01", "run a security audit on production"

  4. First tool call opens your browser for OAuth login: approve, and you're connected. Subsequent calls happen silently.

The tools picker (small icon at the bottom of the chat input) lets you toggle which ManageLM tools the agent may call. Leave them all on for the full surface.

VS Code Extension

The ManageLM extension adds a dedicated @managelm chat participant to Copilot Chat. It ships 33 tools modelled on the ManageLM MCP tools and uses an API key instead of OAuth. Tasks and scans run on one server at a time.

Extension: Install

From the marketplace

Search for ManageLM in the Extensions panel, or run:

terminal
code --install-extension managelm.managelm

From VSIX

Download the .vsix from GitHub Releases and install:

terminal
code --install-extension managelm-1.0.0.vsix

API key setup

  1. Open Settings (Cmd+, / Ctrl+,) and search for ManageLM

  2. Set your API Key, created in your ManageLM portal under Settings > MCP & API > API Keys. The key acts as you, limited to the authorizations you tick: add Reports for scans, Hosting for VM actions, Credentials or Keystore to search those.

  3. (Optional) If self-hosting, set the Portal URL to your own portal address

Extension: Use

Daily usage

Open Copilot Chat (any mode) and type @managelm followed by your request:

copilot chat
@managelm show me all my servers
@managelm check disk usage on web-prod-01
@managelm install nginx on web-staging-02
@managelm run a security audit on db-primary
@managelm which servers are running Docker?
@managelm which certificates expire this month?

Tools shipped with the extension

ToolDescription
search_agentsServers by status, group, site, health or text
get_agent_infoOne server: OS, health, skills, recent tasks
get_agent_skills / list_available_skillsSkills on a server, catalog skills not yet imported
get_account_info / list_team_membersAccount, groups and sites, team members
search_inventory / search_security / search_activityInventory, security issues (audits, pentests, threats), logins and sudo
search_ssh_keys / search_sudo_rulesAccess across the fleet, mapped to your team
search_certificates / search_pkiCertificates found on servers, certificates ManageLM issues
search_monitors / search_backupsMonitors with current status, backups and their last run
search_credentials / search_keystoreRotating credentials, keystore keys and usage (metadata only)
list_connectors / search_cloud / get_cloud_infoHosting connectors and the resources they discover
cloud_actionStart, stop, reboot or snapshot a VM (disruptive actions need your confirmation)
run_security_audit / run_inventory_scan / run_access_scan / run_certificate_scan / run_activity_scanRun a scan on one server and wait for the result
run_taskRun a skill-based task on one server (auto lets the agent pick the skill)
answer_task / follow_up_taskAnswer a task waiting for input, continue a conversation
get_task_status / get_task_history / get_task_changes / revert_taskTask results, history, file changes and revert

What You Can Do

Either integration lets you:

With MCP, tasks and scans can also target a group, a site or the whole fleet with "all", and every skill gets its own tool. The extension runs tasks through one tool with a skill parameter, on one server at a time.

Security

Requirements

Troubleshooting

MCP: "Install MCP" deeplink does nothing

Make sure VS Code is installed and registered as the vscode:// protocol handler. Open VS Code first, then click the deeplink again. If it still fails, use the manual config above.

MCP: Server is "Started" but no tools appear

Switch the chat mode to Agent (the tools picker only shows in Agent mode). If still empty, type a request directly. The OAuth flow runs on first call and tools register after authentication.

MCP: OAuth fails in Safari

Safari's Intelligent Tracking Prevention can block the loopback callback. Switch your default browser to Chrome or Firefox for the sign-in step, then switch back. Auth tokens persist after.

Extension: API key not configured

Open VS Code Settings (Ctrl+,), search for ManageLM, and enter your API key from the portal under Settings > MCP & API.

Extension: @managelm not appearing in chat

The extension requires GitHub Copilot Chat. Make sure github.copilot-chat is installed and active. Reload VS Code (Ctrl+Shift+P > Reload Window) after enabling.

Connection refused or timeout (both)

Verify your portal URL is correct and reachable. Default is https://app.managelm.com. If self-hosting, make sure your portal is running and accessible from your machine.

No agents listed (both)

Either no agents are enrolled, or your account doesn't have access. Check the portal dashboard to verify.

Task timeout

With the extension, a task still running after 2 minutes is reported with its task ID: ask @managelm to check its status a bit later. Long operations can also be broken into smaller steps.