Gibil

io.github.AlexikMPublished by GitHub account AlexikMv0.5.1Updated Oct 24, 2026

Spawns an ephemeral Ubuntu VM with project clone, shell exec, file I/O, and auto-destroy on TTL.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Gibil lets an assistant spin up a temporary Ubuntu VM to clone a project, run shell commands, and read or write files, then auto-destroy it.

What you can do
Gibil provisions an ephemeral Ubuntu virtual machine and exposes it to the assistant as a working environment. According to the description, it can clone a project into the VM, execute shell commands, perform file input and output, and destroy the machine automatically when a time-to-live expires. It targets cloud providers such as Hetzner and Vultr, and can optionally clone private GitHub repositories at boot.
When to use it
Use it when an assistant needs a disposable Linux environment for a task: running builds or scripts, inspecting or editing a project in isolation, or testing something without touching the local machine. It suits short-lived, self-cleaning workloads rather than persistent servers.
Requirements
Runs locally over stdio, typically installed from the npm package gibil, and is desktop-only. At least one cloud provider token is required: HETZNER_API_TOKEN for Hetzner or VULTR_API_KEY for Vultr. GIBIL_API_KEY is optional for usage tracking and paid plans, and GITHUB_TOKEN is optional for cloning private repositories. Network access to the chosen provider is needed.
Before you install
The server asks for cloud provider API tokens (HETZNER_API_TOKEN, VULTR_API_KEY) that can create and destroy billable infrastructure, so usage may cost money. GITHUB_TOKEN grants access to private repositories, and GIBIL_API_KEY ties usage to a gibil.dev account. The assistant can run arbitrary shell commands and write files inside the VM, and the VM is destroyed automatically at the end of its TTL, so unsaved work is lost.

Installation

In SourceWeft

  1. Open Gibil in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.5.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.