English Français العربية

SAGE Wrapper

Official registry Developer tools

Command wrapper MCP server for coding agents, compression, workflows, and local automation.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

PYPI package psycgod-sage
Claude Code 
claude mcp add sage-wrapper -- uvx psycgod-sage==2.6.2
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "sage-wrapper": {
            "command": "uvx",
            "args": [
                "psycgod-sage==2.6.2"
            ]
        }
    }
}
NPM package psycgod-sage
Claude Code 
claude mcp add sage-wrapper -- npx -y psycgod-sage@2.6.2
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "sage-wrapper": {
            "command": "npx",
            "args": [
                "-y",
                "psycgod-sage@2.6.2"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. SAGE - Smart Agent Guidance Engine
  2. Start Here: Install SAGE, Use once sage run -- python -m pytest, Then Use Any AI Agent
  3. What SAGE Does
  4. Recorded Local Metrics
  5. Why It Helps
  6. Distribution
  7. Common Commands
  8. Privacy Modes
  9. Known Limitations
  10. Demos
  11. Links
  12. License

SAGE - Smart Agent Guidance Engine

SAGE is a local-first command wrapper for AI coding agents. It keeps full terminal output on your machine, sends agents a clean compressed summary, and tracks proof metrics without uploading your raw logs.

Use it with Claude Code, Codex, Cursor, Windsurf, OpenCode, Cline, custom agents, CI scripts, and normal terminal workflows.

Start Here: Install SAGE, Use once sage run -- python -m pytest, Then Use Any AI Agent

Package installation is passive for package-registry safety. After installing, run sage install once to activate SAGE for supported local AI agents.

PyPI / pip
pip install psycgod-sage
# or
python -m pip install --upgrade psycgod-sage
sage install
sage run -- python -m pytest
npm / npx
npm install -g psycgod-sage
npx -y psycgod-sage install
npx -y psycgod-sage run -- npm test

After install, restart any open AI-agent sessions. New sessions should read the SAGE instructions automatically and route terminal commands through SAGE.

Example prompt after restarting your AI agent:

Please help me with my general book in this folder.

Natural shortcuts also work:

sage pytest
sage npm test
sage git status

These are treated as:

sage run -- pytest
sage run -- npm test
sage run -- git status

What SAGE Does

StepResult
sage installActivates the machine locally, repairs global/project agent instructions, and verifies activation
sage run -- <command>Runs the command, stores raw output locally, and returns a compact useful summary
Agent memory/hooksTell supported AI agents to use SAGE for noisy terminal work
Local databaseKeeps command history, compression proof, and retry context on the user's machine
Local proofKeeps command and compression metrics on the user's machine

SAGE does not auto-enable MCP. MCP is optional and manual for users who want it.

Recorded Local Metrics

Latest pulled stats as of 2026-08-01:

MetricValue
SAGE telemetry command events27,892
Tokens processed799.5M
Tokens saved783.7M
Compression rate98.02%
Estimated savings$16,261.90
Command success rate88.3%
PyPI downloads, last 7 days632
npm downloads, last 7 days362
GitHub clones, last 14 days574

Why It Helps

AI coding agents burn context on repeated logs, failed test output, install noise, stack traces, and build spam. SAGE sits between the command and the agent.

Without SAGEWith SAGE
Agent sees full noisy terminal outputAgent sees the useful summary
Context disappears fastContext lasts longer
Repeated failures waste tokensErrors are grouped and explained
Raw logs may enter promptsRaw logs stay local
Hard to prove savingsSAGE records proof metrics

Distribution

ChannelPackageStatus
PyPIpsycgod-sageCanonical Python package
npm / npxpsycgod-sageNode launcher for the Python core
MCP Registryio.github.PsYcGoD/sageOptional/manual MCP entry
GlamaPsYcGoD/sageOptional/manual hosted MCP listing

The npm package delegates to the Python implementation so both install paths use the same local database, telemetry rules, compression, and command behavior.

Common Commands

sage install                       # Activate this machine and AI-agent instructions
sage doctor --activation           # Verify activation
npx -y psycgod-sage doctor --activation
sage run -- <command>              # Wrap any command
sage run --cwd /project -- <command> # Explicit workspace for host integrations
sage pytest                        # Shortcut for: sage run -- pytest
sage npm test                      # Shortcut for: sage run -- npm test
sage git status                    # Shortcut for: sage run -- git status
sage context stats                 # Token savings summary
sage context report                # Full compression report
sage history --limit 10            # Recent command history
sage explain --failed              # Explain the latest failed command
sage suggest --failed              # Suggest the next fix
sage fix --apply                   # Try an automatic fix
sage ml setup                      # Optional ML V2 dependencies
sage mcp install                   # Optional/manual MCP config
sage dashboard start               # Local dashboard

Privacy Modes

ModeRequires login?Sends data?What leaves the machine?
Local-onlyNoNoNothing
Debug telemetryOptionalOpt-in onlyRedacted diagnostic summaries

SAGE is designed to keep prompts, source code, credentials, raw command output, and project files local unless the user deliberately enables a feature that requires sending data.

Known Limitations

LimitationWhat To Do
Already-open AI-agent sessions may not reload new instructionsRestart Claude/Codex/Cursor/Windsurf/OpenCode after sage install
Locked-down host apps can disable shell toolsSAGE cannot enable tools the host application has blocked
A host starts its shell in the wrong folderPass sage run --cwd <project> -- <command> or set SAGE_WORKSPACE_CWD
npm/PyPI installs cannot safely auto-run activationRun sage install once after package install
MCP can disconnect in some stdio agent sessionsUse normal sage run -- <command> by default; enable MCP manually only if needed
Package installs are passive by designReal activation starts with sage install

Demos

FlowPreview
PyPI install
npm install
sage run --
CLI run

License

MIT. See LICENSE.

Frequently asked questions

What is SAGE Wrapper?

Command wrapper MCP server for coding agents, compression, workflows, and local automation.

How do I install SAGE Wrapper?

It runs on your machine. In Claude Code: claude mcp add sage-wrapper -- uvx psycgod-sage==2.6.2. For other clients, paste the JSON configuration from this page into their MCP settings.

Does SAGE Wrapper need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is SAGE Wrapper open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains SAGE Wrapper?

It is published by PsYcGoD. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.