Global Executables MCP Server

What the code does

We read the source, 6 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        select {
        case <-ctx.Done():
            return ctx.Err()
        case sendCh <- next:
            submitted++
            active++

        filepath.Join(root, stateManifestName),

        cargo = subprocess.run(["cargo", "metadata", "--format-version", "1", "--no-deps", "--manifest-path", str(manifest)], check=True, capture_output=True, text=True)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add global-executables -- uvx global-executables

{
  "mcpServers": {
    "global-executables": {
      "command": "uvx",
      "args": [
        "global-executables"
      ]
    }
  }
}

[mcp_servers.global-executables]
command = "uvx"
args = ["global-executables"]

{
  "mcpServers": {
    "global-executables": {
      "command": "uvx",
      "args": [
        "global-executables"
      ]
    }
  }
}

{
  "servers": {
    "global-executables": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "global-executables"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: GLOBAL_EXECUTABLES_DATASET_ROOT (Optional local checkout of the dictionary branch; when unset, files are fetched on demand over HTTPS and cached), GLOBAL_EXECUTABLES_CACHE_DIR (Optional cache directory for fetched dataset files), GLOBAL_EXECUTABLES_OFFLINE (Set to 1 to serve only cached files and never touch the network).