Skip to main content
Aescut MCP

How Do I Install The Aescut MCP Server?

What the Aescut installer actually does today, when to use the generic bundle, and how to wire the MCP manually.

Short answer

The cleanest path is the Aescut installer package. It writes a generic agent bundle containing an MCP config snippet plus the guard prompt, and it can optionally patch Claude Desktop directly. It does not claim to auto-modify every AI client on earth.

If you prefer full control, you can also add the Aescut MCP manually by pointing a client at @aeptus/aescut --skip-install with the right launcher and CMS URL.

Recommended path

  1. 01

    Run the installer

    Use npx -y @aeptus/aescut, or an equivalent launcher such as pnpm dlx, yarn dlx, bunx, or volta run npx.

  2. 02

    Merge the generated mcp.json into your client

    The installer writes a generic bundle under ~/.aescut/install unless you tell it to target a specific config path.

  3. 03

    Add the guard prompt if you want policy guidance

    The MCP exposes the data; the guard prompt is what nudges an agent to consult the registry before installing or recommending tools.

One-command install

npx -y @aeptus/aescut

Equivalent launchers are documented for pnpm dlx, yarn dlx, bunx, volta run npx, and Homebrew. The installer’s default output is intentionally host-agnostic, because different agents store MCP config in different places.

What the installer writes

The generic bundle includes:

  • mcp.json with the Aescut MCP server config
  • aescut-guard.md for system-prompt style hosts
  • aescut-guard.skill.md for skill-style hosts
  • A README explaining how to merge the files into the target client
{
  "mcpServers": {
    "aescut": {
      "command": "npx",
      "args": ["-y", "@aeptus/aescut", "--skip-install"],
      "env": {
        "SAFE_SKILLS_CMS_URL": "https://cms.aescut.dev"
      }
    }
  }
}

When to configure it manually

Manual setup is still the better option when you want the configuration checked into a repository, wrapped in MDM, or generated by another onboarding tool. Aescut’s own package docs explicitly support that path and document the launcher mapping.

Sources and further reading