Skip to main content
Glama
Arrakis MCP Server

Arrakis MCP Server

by abshkbh

Arrakis MCP Server

A Model Context Protocol (MCP) server that exposes Arrakis VM sandbox functionality to Large Language Models.

Setup

Setup

  1. Clone this repository:

    git clone https://github.com/abshkbh/arrakis-mcp-server.git
    cd arrakis-mcp-server
  2. Configure your LLM tool to use the Arrakis MCP server by adding the following to your MCP configuration:

    "mcpServers": {
        "arrakis": {
            "command": "<path-to-uv>",
            "args": [
                "--directory",
                "<path-to-repo>",
                "run",
                "arrakis_mcp_server.py"
            ]
        }
    }

Related MCP server: agent-sandbox-mcp

API

The Arrakis MCP Server exposes the following MCP resources and tools:

Resources

  • arrakis://vms - List all available VMs

  • arrakis://vm/{vm_name} - Get information about a specific VM

Tools

  • start_sandbox - Start a new VM sandbox

  • restore_snapshot - Restore a VM from a snapshot

  • snapshot - Create a snapshot of a VM

  • run_command - Run a command in a VM

  • upload_file - Upload a file to a VM

  • download_file - Download a file from a VM

  • destroy_vm - Destroy a specific VM

  • destroy_all_vms - Destroy all VMs

  • update_vm_state - Update the state of a VM (pause/stop)

License

This project is licensed under the GNU Affero General Public License v3.0 - see the LICENSE file for details.

Available Tools

9 tools
destroy_all_vmsC

Destroy all VMs.

Returns: Success/failure message.

Inputs: no named parameters.

destroy_vmB

Destroy a VM.

Args: vm_name: Name of the VM to destroy.

Returns: Success/failure message.

Inputs: vm_name (required).

download_fileB

Download a file from a VM.

Args: vm_name: Name of the VM to download from. path: Path of the file to download.

Returns: Content of the file or error message.

Inputs: vm_name (required), path (required).

restore_snapshotC

Restore a VM from a snapshot.

Args: vm_name: Name to give to the restored VM. snapshot_id: ID of the snapshot to restore from.

Returns: Information about the restored VM.

Inputs: vm_name (required), snapshot_id (required).

run_commandB

Run a command in a VM.

Args: vm_name: Name of the VM to run the command in. cmd: Command to execute.

Returns: Command output and/or error.

Inputs: vm_name (required), cmd (required).

snapshotA

Create a snapshot of a VM.

Args: vm_name: Name of the VM to snapshot. snapshot_id: Optional ID for the snapshot. If not provided, one will be generated.

Returns: ID of the created snapshot.

Inputs: vm_name (required), snapshot_id.

start_sandboxB

Start a new sandbox VM.

Args: name: Name to give to the new VM.

Returns: Information about the created VM.

Inputs: name (required).

update_vm_stateA

Update the state of a VM.

Args: vm_name: Name of the VM to update. status: New state for the VM. Must be either 'stopped' or 'paused'.

Returns: Success/failure message.

Inputs: vm_name (required), status (required).

upload_fileB

Upload a file to a VM.

Args: vm_name: Name of the VM to upload to. path: Destination path in the VM. content: Content of the file.

Returns: Success/failure message.

Inputs: vm_name (required), path (required), content (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: starting, destroying, snapshotting, restoring, file operations, command execution, and state updates. No two tools overlap in functionality.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., destroy_vm, download_file, restore_snapshot). The tool 'snapshot' is a slight outlier as it uses a noun as a verb, but it is still clear.

    Tool Count5/5

    With 9 tools covering creation, destruction, state management, snapshots, file transfer, and command execution, the count is well-scoped for a VM management server.

    Completeness2/5

    There are significant gaps: no tool to list VMs or snapshots, and no way to get VM status. These missing query operations will cause agent failures when trying to discover existing resources.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers