Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
作者提供的说明(英文原文)
Orbit's local-first task and workflow registry for coding agents.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"orbit": {
"command": "npx",
"args": [
"-y",
"@orbit-tools/cli",
"mcp",
"serve"
]
}
}
}在终端中运行这条命令
claude mcp add orbit -- npx -y @orbit-tools/cli mcp serve粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"orbit": {
"command": "npx",
"args": [
"-y",
"@orbit-tools/cli",
"mcp",
"serve"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"orbit": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@orbit-tools/cli",
"mcp",
"serve"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 constellation-works 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.19.0)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Agent-Native Google Calendar - manage events, sync, and public booking
Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Agents write. Orbit delivers.
Orbit is a local-first runtime for coding agents. Keep using your authenticated agent CLI; Orbit adds a durable task queue, sandboxed worktrees, file locks for parallel runs, a gated delivery pipeline, and an audit log.
Why: fast agents make planning, review, and traceability easy to lose. Orbit keeps the prompt, plan, and review behind every change, with a task ID on every workflow commit.
~/.orbit and .orbit/; Orbit sends no telemetry.You: The fsProfile lookup is undocumented. Get that fixed.
Agent: Files a proposed task with acceptance criteria. Approve it and ship? You: Yes. Agent: Queues it, then runs plan → execute → review in a locked, isolated worktree. Opens a pull request. Review and merge it, then approve the task to close it.
Nothing starts without approval; PR runs stop for your review unless you authorize --complete. The task record keeps the prompt, plan, execution trace, and review. For larger specs, ask your agent to orchestrate: the bundled orbit-orchestrate skill splits the work, queues it once approved, runs it in parallel, and diagnoses failures (delivery workflows).
You need: macOS or Linux (x64 or arm64; Windows uses WSL2), Node 18+, an authenticated agent CLI, and authenticated gh for pull requests.
npm install -g @orbit-tools/cli
orbit init # machine name, task-ID prefix, agent skills, and Linux sandbox setup
Open your agent in the repo and ask it to “set up Orbit for this repo”. The bundled orbit-setup skill registers it, connects MCP, runs orbit doctor, and asks for choices such as the PR target branch. Start a fresh agent session, then ask: “Add a hello.txt file containing hello; file it as an Orbit task.” Approve and ship the task when prompted, review and merge the PR, then approve the task to close it. Watch with orbit web serve.
Prefer a plugin? Install Orbit for Claude Code, Codex, or Cursor. Every MCP tool has a CLI twin; for the same loop without an agent, see your first task from the terminal.
Set up the repo by hand
cd <repo> && orbit workspace init --mcp # add --ship-mode local to skip PRs
orbit doctor orbit web serve
Review and commit the checkout files listed by workspace init, including MCP client files, before the first ship. Local delivery refuses tracked changes, merge conflicts, and untracked paths overlapping incoming changes.
orbit doctor checks CLI presence for default, system, and complexity-routed crews and warns when no MCP client is registered; it does not check provider sign-in or MCP connectivity. Use orbit doctor providers for all executor definitions. See Linux sandbox readiness and distro coverage.
| To… | Run |
|---|---|
| Inspect a task or run | orbit task show · orbit run show |
| Open the dashboard | orbit web serve (remote: orbit web connect ) |
| Open the dashboard in a desktop window | Build the app in desktop/ |
| Pick the default crew (provider and model) | orbit config set workflow.default_crew |
| Route tasks to crews by complexity | orbit config set --global workflow.hard_complexity_crews '["opus"]' (more) |
| Upgrade | npm install -g @orbit-tools/cli@latest (orbit update --check shows what's new) |
Crews name a provider, model, and effort level; complexity pools choose one for a task without an explicit crew. See crew definitions, init's seeded pools, and complexity routing, weighting, and overrides.
Connect your agent explains operator and agent-only authority; federated MCP connects multiple machines.
Scoping rules explain machine and workspace state. See the runbooks for backups, recovery, and upgrades.
Pull requests are welcome, from typo fixes to new executors. Small fixes can go straight to a PR; bigger changes start with an issue. See CONTRIBUTING.md.
MIT