What is the key difference between Sage and Execkit?

Sage belongs to the Command Line category with local stdio execution, while Execkit belongs to the Command Line category with local stdio execution.

How do I install Sage or Execkit in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Sage and Execkit free or paid?

Sage operates under a Free / Open Source model (No auth required). Execkit operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Sage lists 6 tools with 5 views and 10 GitHub stars. Execkit lists 6 tools with 3 views and 7 GitHub stars.

Can I use both Sage and Execkit together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Sage vs Execkit

In-depth architectural comparison of the Sage and Execkit MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Sage

Command Line · Local stdio

Quality: 56/100 (Good) | Auth: No auth required

Execkit

Command Line · Local stdio

Quality: 60/100 (Good) | Auth: No auth required

Verdict Summary: Choose Sage if you need specialized Command Line tools running via a local process. Choose Execkit if your workspace requires Command Line integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Sage when:

You need dedicated capabilities in the Command Line domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Local shell command wrapper, Compressed terminal summaries, Local command history and retry context.

Explore Sage Details

Choose Execkit when:

You need dedicated capabilities in the Command Line domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: session_checkpoint, session_checkpoints, session_create.

Explore Execkit Details

Feature & Specification Comparison

Specification	Sage PsYcGoD Command Line	Execkit blinkingbit-oss Command Line
Summary	Local-first CLI and MCP wrapper for AI coding agents. Routes shell commands through sage run --, stores command history locally, and returns compressed terminal output to reduce context noise.	Stateful, structured, auditable shell sessions for AI agents over local, SSH, and Docker. Secret redaction, output budgeting, SSH host-key verification, and a loopback read-only browser viewer that streams the live transcript.
Category & Scope

Tools & Capabilities Breakdown

Sage Tools (6)

Local shell command wrapper

Compressed terminal summaries

Local command history and retry context

Context statistics and compression reports

Failure explanations and fix suggestions

Optional manual MCP configuration

Execkit Tools (6)

session_checkpoint

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Sage Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "psycgod-sage": {
      "command": "npx",
      "args": [
        "-y",
        "psycgod-sage"
      ]
    }
  }
}

Execkit Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "blinkingbit-oss-execkit": {
      "command": "uvx",
      "args": [
        "execkit-mcp"
      ]
    }
  }
}

Frequently Asked Questions

Sage is categorized under Command Line and uses a local stdio subprocess. In contrast, Execkit belongs to Command Line using local stdio subprocess. Select Sage when you need capabilities focused on command line and Execkit when you require tools for command line.

More alternatives to Sage More alternatives to Execkit Command Line category hub Canonical compare URL