Sugar

Name: Sugar
Author: roboticforce

作者：roboticforce版本 3.4.2i★ –i在你的电脑上运行

注册名称io.github.cdnsteve/sugar

安装

概览

作者提供的说明（英文原文）

Autonomous AI development system with persistent task queue and background execution

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 0 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 文档、表格与办公

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 0 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： ANTHROPIC_API_KEY, GITHUB_TOKEN, SUGAR_DEFAULT_REPO

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "sugar": {
      "command": "uvx",
      "args": [
        "sugarai",
        "mcp",
        "serve"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "your-value",
        "GITHUB_TOKEN": "your-value",
        "SUGAR_DEFAULT_REPO": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add sugar --env ANTHROPIC_API_KEY=your-value --env GITHUB_TOKEN=your-value --env SUGAR_DEFAULT_REPO=your-value -- uvx sugarai mcp serve

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "sugar": {
      "command": "uvx",
      "args": [
        "sugarai",
        "mcp",
        "serve"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "your-value",
        "GITHUB_TOKEN": "your-value",
        "SUGAR_DEFAULT_REPO": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "sugar": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "sugarai",
        "mcp",
        "serve"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "your-value",
        "GITHUB_TOKEN": "your-value",
        "SUGAR_DEFAULT_REPO": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

ANTHROPIC_API_KEY env
Anthropic API key for Claude model access
GITHUB_TOKEN env
GitHub token for repository access
SUGAR_DEFAULT_REPO env
Default repository in owner/repo format

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

! 注意
作者与仓库一致
发布者（cdnsteve）不是仓库所有者（roboticforce）；可能是其他人代为上架的
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“文档、表格与办公”中的其他服务器比较i

星标数多于此分类中其他 2186 个服务器的 0%
发布到注册中心的时间比此分类中其他 2186 个服务器的 2% 更新
基础检查结果等于或优于此分类中其他 2186 个服务器的 32%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Sugar 安全吗？

它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（3.4.2）于10个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Agent-Native Calendar

作者：BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

在云端运行★ 7,620MIT2个月前更新

安装

Excel MCP Server

作者：haris-musa

Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.

在你的电脑上运行★ 4,276MIT6天前更新

安装

MCP Server for Excel

作者：sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

在你的电脑上运行★ 847MIT3天前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Sugar

Persistent memory for AI coding agents.

Your AI agent starts every session with amnesia. The architecture decisions, conventions, and gotchas you explained last week are gone. Sugar is the local-first memory layer that remembers them for you - per project, across projects, on your machine.

Your memory. Your machine. Your data.

What Sugar Does

Sugar is a memory layer your AI coding agent can read and write directly:

Project memory - Decisions, preferences, error patterns, and research stored per-project
Global memory - Standards and guidelines shared across every project you work on
Semantic search - Retrieve relevant context by meaning, not just keywords
MCP integration - Your AI agent reads and writes memory directly during sessions
Local-first - SQLite on your disk, no API keys, fully offline-capable
Task queue - Optional autonomous execution, powered by the same memory layer

Quick Start

# Install once, use in any project

pipx install sugarai

Initialize in your project

cd ~/dev/my-app sugar init

Store what you know

sugar remember "We use async/await everywhere, never callbacks" --type preference sugar remember "JWT tokens use RS256, expire in 15 min - see auth/tokens.py" --type decision sugar remember "When tests fail with import errors, check init.py exports first" --type error_pattern

Retrieve it later

sugar recall "authentication" sugar recall "how do we handle async"

Your AI agent can also read and write memory directly - no copy-pasting required.

MCP Integration

Connect Sugar's memory to your AI agent so it can access project context automatically.

Claude Code - Memory server (primary):

claude mcp add sugar -- sugar mcp memory

Claude Code - Task server (optional):

claude mcp add sugar-tasks -- sugar mcp tasks

Once connected, Claude can call store_learning to save context mid-session and search_memories to pull relevant knowledge before starting work. The memory server works from any directory - global memory is always available even outside a Sugar project.

Other MCP clients (Goose, Claude Desktop):

# Goose

goose configure

Select "Add Extension" -> "Command-line Extension"

Name: sugar

Command: sugar mcp memory

OpenCode - one command setup

sugar opencode setup

Skills

Sugar ships Agent Skills - folders of instructions that teach coding agents to apply Sugar's methodology. Skills live under skills/ and follow the Agent Skills specification (a SKILL.md with name/description frontmatter plus instructions).

Skill	What it does
`sugar-memory`	Store and surface project context via Sugar's memory MCP server: recall context at task start, search before deciding, store learnings after completing work
`sugar-task-planner`	Turn a high-level task into a detailed execution plan: subtasks, dependencies, time estimates, risks, and measurable success criteria
`sugar-quality-guardian`	Review code across quality, testing, security, and performance, ending with a structured verdict
`sugar-orchestrator`	Coordinate multi-step workflows: analyze complexity, decompose tasks, assign roles, monitor execution

Each skill includes an evaluation dataset (evals/evals.json) and is measured with NVIDIA SkillEvaluator against the OpenCode harness. See Skill Benchmarks for the Skill Lift results - sugar-memory and sugar-task-planner both show measured positive lift.

Global Memory

Some knowledge belongs to you, not just one project. Coding standards, preferred patterns, security practices - these should follow you everywhere.

# Store a guideline that applies to all your projects

sugar remember "Always validate and sanitize user input before any DB query" \ --type guideline --global

sugar remember "Use conventional commits: feat/fix/chore/docs/test" \ --type guideline --global

View your global guidelines

sugar recall "security" --global sugar memories --global

Search works project-first, but guidelines always surface

sugar recall "database queries"

Returns: project-specific memories + relevant global guidelines

Global memory lives at ~/.sugar/memory.db. Project memory lives at .sugar/memory.db. When you search, project context wins - but guideline type memories from global always appear in results so your standards stay visible.

Via MCP, pass scope: "global" to store_learning to save cross-project knowledge directly from your AI session.

Memory types: decision, preference, file_context, error_pattern, research, outcome, guideline

Full docs: Memory System Guide

How Memory Works

Sugar uses two SQLite databases and a tiered search strategy.

Two stores:

Project store (.sugar/memory.db) - context specific to one project
Global store (~/.sugar/memory.db) - knowledge that applies everywhere

Seven memory types, each with different retrieval behavior:

Type	Purpose	TTL
`decision`	Architecture and implementation choices	Never
`preference`	How you like things done	Never
`file_context`	What files and modules do	Never
`error_pattern`	Bugs and their fixes	90 days
`research`	API docs, library findings	60 days
`outcome`	What worked, what didn't	30 days
`guideline`	Cross-project standards and best practices	Never

Search strategy - project-first with reserved guideline slots:

Search the project store first (local context always wins)
Reserve slots for global guidelines (cross-project standards always surface)
Fill remaining slots with other global results
Deduplicate across both stores

This means a mature project's local context dominates results. A new project with no local memory gets global knowledge automatically. And your guidelines are always visible regardless.

Search engine: Semantic search via sentence-transformers (all-MiniLM-L6-v2, 384-dim vectors) with sqlite-vec. Falls back to SQLite FTS5 keyword search, then LIKE queries. No external API calls - everything runs locally.

# Install with semantic search (recommended)

pipx install 'sugarai[memory]'

Works without it too - just uses keyword matching

pipx install sugarai

MCP tools available to your AI agent:

Tool	What it does
`search_memory`	Search both stores, returns results with scope labels
`store_learning`	Save a memory (pass `scope: "global"` for cross-project)
`recall`	Get formatted markdown context for a topic
`get_project_context`	Full project summary including global guidelines
`list_recent_memories`	Browse recent memories by type

MCP resources:

sugar://project/context - project summary
sugar://preferences - coding preferences
sugar://global/guidelines - cross-project standards

Task Queue

The task queue lets you hand off work and let it run autonomously. It reads from the same memory store, so Sugar already knows your preferences and patterns before it starts.

# Add tasks

sugar add "Fix authentication timeout" --type bug_fix --urgent sugar add "Add user profile settings" --type feature

Start the autonomous loop

sugar run

Sugar picks up tasks, executes them with your configured AI agent, runs tests, commits working code, and moves to the next task. It runs until the queue is empty or you stop it.

Delegate from Claude Code mid-session:

/sugar-task "Fix login timeout" --type bug_fix --urgent

Advanced task options: New in 3.10: Task Orchestration decomposes large features into a 4-stage workflow (research, plan, implement, review) with specialist agent routing and dependency-ordered sub-tasks.

# Orchestrated execution - 4-stage workflow (New in 3.10)

sugar add "Add OAuth authentication" --type feature --orchestrate

Iterative mode - loops until tests pass

sugar add "Implement rate limiting" --ralph --max-iterations 10

Check queue status

sugar list sugar status

Full docs: Task Orchestration

Autonomous Issue Resolution (optional)

Because Sugar remembers your codebase and conventions, it can also resolve routine issues autonomously. Point it at a GitHub repo, configure which labels to act on (security, bug, dependabot), and Sugar will read each issue, implement the fix, run your tests, and open a PR.

Labeled issue appears on GitHub

-> Sugar picks it up (label filter: "security", "dependabot", "bug") -> AI agent reads the issue, analyzes the affected code -> Fix implemented, tests run locally -> PR opened - you review and merge

This is one application of the memory layer, not the headline. Use Sugar purely as memory, or enable resolution - your choice. See workflow examples for security auto-fix, bug triage, test coverage, and more.

Supported AI Tools

Works with any CLI-based AI coding agent:

Agent	Memory MCP	Task MCP	Notes
Claude Code	Yes	Yes	Full support
OpenCode	Yes	Yes	`sugar opencode setup`
Goose	Yes	Yes	Via MCP
Aider	Via CLI	Via CLI	Manual recall

Installation

Recommended: pipx - installs once, available everywhere, no venv conflicts:

pipx install sugarai

Upgrade / Uninstall:

pipx upgrade sugarai

pipx uninstall sugarai

Other installation methods

pip (requires venv activation each session)

pip install sugarai

uv pip install sugarai

With semantic search (recommended for memory):

pipx install 'sugarai[memory]'

With GitHub integration:

pipx install 'sugarai[github]'

All features:

pipx install 'sugarai[all]'

Sugar is project-local by default. Each project gets its own .sugar/ folder with its own database and config. Global memory lives at ~/.sugar/. Like git - one installation, per-project state.

Project Structure

~/.sugar/

└── memory.db # Global memory (guidelines, cross-project knowledge)

~/dev/my-app/ ├── .sugar/ │ ├── sugar.db # Project memory + task queue │ ├── config.yaml # Project settings │ └── prompts/ # Custom agent prompts └── src/

Recommended .gitignore:

.sugar/sugar.db

.sugar/sugar.log .sugar/*.db-*

Commit .sugar/config.yaml and .sugar/prompts/ to share settings with your team.

Configuration

.sugar/config.yaml is created on sugar init:

sugar:

dry_run: false loop_interval: 300 max_concurrent_work: 3

claude: enable_agents: true

discovery: github: enabled: true repo: "user/repository"

Documentation

Quick Start
Memory System
Skill Benchmarks
CLI Reference
Task Orchestration
Goose Integration
OpenCode Integration
GitHub Integration
Configuration Guide
Troubleshooting

Requirements

Python 3.11+
A CLI-based AI agent: Claude Code, OpenCode, Aider, or similar

Contributing

Contributions welcome. See CONTRIBUTING.md.

git clone ht

只显示了开头部分；其余内容请在仓库中阅读

Sugar

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“文档、表格与办公”中的其他服务器比较i

常见问题

替代选择

Agent-Native Calendar

Excel MCP Server

MCP Server for Excel

作者的 README

Sugar

What Sugar Does

Quick Start

Initialize in your project

Store what you know

Retrieve it later

MCP Integration

Select "Add Extension" -> "Command-line Extension"

Name: sugar

Command: sugar mcp memory

OpenCode - one command setup

Skills

Global Memory

View your global guidelines

Search works project-first, but guidelines always surface

Returns: project-specific memories + relevant global guidelines

How Memory Works

Works without it too - just uses keyword matching

Task Queue

Start the autonomous loop

Iterative mode - loops until tests pass

Check queue status

Autonomous Issue Resolution (optional)

Supported AI Tools

Installation

Project Structure

Configuration

Documentation

Requirements

Contributing