Aicoreutils

io.github.caseSHYPublished by GitHub account caseSHYv0.3.6Updated Oct 24, 2026

JSON-first Coreutils CLI for AI agents. 114 commands with sandbox, dry-run, and MCP support.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local JSON-first coreutils-style CLI exposing 114 commands to an AI assistant, with sandbox and dry-run options.

What you can do
Provides a command-line utility collection designed for AI agents, described as JSON-first and covering 114 commands. It supports a sandbox mode and a dry-run mode, and is exposed to assistants over MCP. The manifest lists no individual tools, so the exact command set is not documented here.
When to use it
Consider it when an assistant needs general-purpose local command execution with structured JSON output, and you want sandboxing or dry-run previews before changes take effect. It is a desktop-only local process, so it does not suit hosted or browser-based setups.
Requirements
Runs as a local process over stdio, installed from the PyPI package aicoreutils, so a Python environment is needed. Desktop only; no web execution. No authentication, environment variables, or headers are declared.
Before you install
The description mentions a sandbox and dry-run, but no details are given about what the sandbox restricts or which commands write, change, or delete data. Review the command set and sandbox behavior before granting an assistant access to your machine.

Installation

In SourceWeft

  1. Open Aicoreutils 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.3.6LatestSep 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.