Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (mcp-chocolatey) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

MCP Chocolatey logo

MCP Chocolatey

Chocolatey on the Model Context Protocol — searchable, installable, upgradable via tools.

license node >=18

🚀 Quick start (Claude Desktop)

Add this entry to claude_desktop_config.json (Windows path: C:\Users\<you>\AppData\Roaming\Claude\claude_desktop_config.json).

{
  "mcpServers": {
    "chocolatey": {
      "command": "npx",
      "args": ["-y", "mcp-chocolatey"],
      "env": {
        "NPX_SILENT": "1",
        "npm_config_loglevel": "silent"
      }
    }
  }
}

Restart Claude Desktop. Then try:

"List installed Chocolatey packages" (uses choco_list)
"Search for 7zip on Chocolatey" (uses choco_search)
"Check outdated Chocolatey packages" (uses choco_outdated)

💡 Tip: If your environment chatters on npx, you can run Node directly:
command: "node", args: ["C:\Users\<you>\AppData\Roaming\npm\node_modules\mcp-chocolatey\src\server.js"].

✨ What you get

⚡ Fully typed MCP tools backed by Chocolatey CLI
🔧 Zero configuration — uses your existing choco install
🖥️ Works in standard Windows terminals and Claude Desktop

🛠️ Tools implemented

choco_list — list local packages (-l)
choco_search — search remote packages (supports --exact, --pre)
choco_install — install by id (optional --version, -y)
choco_upgrade — upgrade by id or all
choco_uninstall — uninstall by id
choco_info — package info (--exact, --verbose)
choco_outdated — list outdated packages
choco_pin — add/remove/list pins
choco_feature — list/enable/disable features
choco_source — list/add/remove/enable/disable/update sources
choco_config — list/get/set/unset config values
choco_help — passthrough help

🔧 Troubleshooting

"Unexpected token … not valid JSON" in Claude logs

Any non‑JSON text on stdout can break MCP. This package avoids stdout noise; however, some environments make npx chatty. Fix: add the env shown above (NPX_SILENT, npm_config_loglevel) or run node directly to the server script.

`choco` not found

Ensure Chocolatey is on PATH. For a per‑user install it typically lives under C:\Users\<you>\AppData\Local\UniGetUI\Chocolatey\bin.

🏗️ Local development

# Start in stdio mode (stdout must be clean for MCP)
npm run start:stdio

📄 License

MIT

mcp-chocolatey