Skip to content

Quick Start

This guide shows the fastest way to run Maverick SSH MCP in streamable HTTP mode (Docker) and in local stdio mode (command line), then connect it to common AI and IDE clients.

What You Need

  • Docker (for HTTP mode), or a local maverick-ssh-mcp installation (for stdio mode).
  • Network access from your MCP client to the server endpoint when using HTTP mode.

Installation (Local)

All packages and binaries are published via Jadaptive Athene:

MCP Bundle (MCPB) - Cross Platform

If your MCP client supports MCP Bundles, this is the simplest single-artifact option.

  • Package format: .mcpb
  • Server type: native binary bundle
  • Target platforms: Linux, macOS, and Windows
  • Target architectures in the bundle:
  • Linux: amd64, arm64
  • macOS: amd64, aarch64
  • Windows: amd64

The MCPB includes platform-specific executables and launcher metadata so the host client can run the right binary for the current OS/architecture.

Usage is typically:

  1. Download maverick-ssh-mcp.mcpb.
  2. Open/import the file in your MCP-capable client.
  3. Confirm the server is installed and available in the client's MCP server list.

If your client does not yet support MCPB, use one of the OS-specific installation options below.

Linux

Debian/Ubuntu (APT repository)

Repository setup instructions: athene.jadaptive.com/r/debian/jadaptive

Install package:

sudo apt update
sudo apt install maverick-ssh-mcp

Red Hat/Rocky/Alma/Fedora (RPM repository)

Repository setup instructions: athene.jadaptive.com/r/rpm/jadaptive

Install package:

sudo dnf install maverick-ssh-mcp

Generic Linux binaries

Example install to /usr/local/bin:

curl -fL -o maverick-ssh-mcp https://athene.jadaptive.com/r/files/jadaptive/maverick-ssh-mcp/current/LINUX/amd64/maverick-ssh-mcp
chmod +x maverick-ssh-mcp
sudo mv maverick-ssh-mcp /usr/local/bin/

macOS

Install .pkg:

Windows

Download executable:

Save maverick-ssh-mcp.exe to a folder in PATH, or call it by full path in your MCP client configuration.

Run with Docker (Streamable HTTP)

Use this when your team wants a shared HTTP MCP endpoint.

docker run --rm -p 7693:7693 -e MCP_TOKEN=replace-with-token jadaptive/maverick-ssh-mcp:latest
  • Default endpoint: http://localhost:7693/mcp
  • Authentication: set MCP_TOKEN and send Authorization: Bearer <token>

Docker Compose Fragment

services:
  maverick-ssh-mcp:
    image: jadaptive/maverick-ssh-mcp:latest
    ports:
      - "7693:7693"
    environment:
      MCP_HOST: 0.0.0.0
      MCP_PORT: 7693
      MCP_TOKEN: ${MCP_TOKEN}

Run Locally (STDIO)

Use this when your MCP client launches local processes directly.

maverick-ssh-mcp --mode stdio

Client Configuration Samples

Configuration keys can vary by client version. Use these as working templates and adjust field names if your client expects a slightly different schema.

VS Code MCP (stdio)

Typical workspace or user settings template:

{
  "mcp": {
    "servers": {
      "maverick-ssh": {
        "type": "stdio",
        "command": "maverick-ssh-mcp",
        "args": ["--mode", "stdio"]
      }
    }
  }
}

Typical config location: VS Code settings.json (workspace .vscode/settings.json or user settings).

Eclipse Copilot (stdio)

Custom MCP server template:

{
  "mcpServers": {
    "maverick-ssh": {
      "command": "maverick-ssh-mcp",
      "args": ["--mode", "stdio"]
    }
  }
}

Typical config location: Eclipse preferences for MCP/Copilot server definitions (or a plugin-managed JSON config file, depending on plugin version).

Opencode (stdio)

Opencode MCP server template:

{
  "mcpServers": {
    "maverick-ssh": {
      "command": "maverick-ssh-mcp",
      "args": ["--mode", "stdio"]
    }
  }
}

Typical config location: Opencode MCP server configuration file or project settings, depending on your Opencode distribution/version.

HTTP Mode Template (for clients that support streamable HTTP)

{
  "mcpServers": {
    "maverick-ssh": {
      "transport": "streamable-http",
      "url": "http://localhost:7693/mcp",
      "headers": {
        "Authorization": "Bearer replace-with-token"
      }
    }
  }
}

Verify the Server Is Reachable

After startup, ask your MCP client to list tools. You should see SSH, shell, local socket, SFTP, SCP, tunnel, and SSH Teams tool groups.