Autonomous AI development system with persistent task queue and background execution
MCPpedia last refreshed this data
Sugar MCP Server is an MCP server that autonomous AI development system with persistent task queue and background execution. Its tool list has not been published yet over stdio, requires no API key, and scores 90/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-cdnsteve-sugar": {
"args": [
"sugarai"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Autonomous AI development system with persistent task queue and background execution
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
uvx 'sugarai' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked sugarai against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in ai-ml / productivity
A cross-platform desktop application for managing AI Agents and MCP Servers. 一款用于管理AI智能体与MCP服务器的跨平台桌面应用程序。
Official MCP server for Anytype API - your encrypted, local and collaborative wiki.
An open-source AI agent that brings the power of Gemini directly into your terminal.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
MCP Security Weekly
Get CVE alerts and security updates for Sugar MCP Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Mission control for your agent fleet.
One durable board for Claude Code, Codex, Cursor, Goose, OpenCode, DSH — and any harness that can claim a task. Atomic claims, live agent activity, cost attribution and tamper-evident history. Local-first, no account.
Quick start · See it work · Why Sugar · Works with · Docs · Team edition
You run four agents across three harnesses on one repo. Then:
A prettier kanban board doesn't fix this. The missing layer is underneath: a durable queue, atomic claims and leases, provenance for every actor, and a history you can replay and export. That's what Sugar is.
Sugar is local-first infrastructure for a fleet of coding agents. Every harness gets the same durable work queue and the same memory. Every claim, transition and tool call lands in an append-only event spine. You watch the fleet in a web dashboard or a native macOS app — on your machine, in your files, with no account.
Your agents keep their own subscriptions and workflows. Sugar doesn't replace Claude Code or Codex; it sits between them and your repo.
sugar add, sugar list, sugar run), MCP tools, REST API and dashboard.--board kanban
(Sugar reads it; Hermes keeps its write path).
~/.sugar/events.db, retention configurable) records every task transition and
every harness event: actor, harness, machine, session, task, project, run and trace id.sugar usage, /api/usage): tokens and cost as you