Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
One canonical, hash-bound package behind every Eclipse social adapter. It publishes nothing itself
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"social-core": {
"command": "uvx",
"args": [
"eclipse-social-core"
]
}
}
}在终端中运行这条命令
claude mcp add social-core -- uvx eclipse-social-core粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"social-core": {
"command": "uvx",
"args": [
"eclipse-social-core"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"social-core": {
"type": "stdio",
"command": "uvx",
"args": [
"eclipse-social-core"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 CYAN-ECLIPSE-TECHNOLOGIES-LLC 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.1)于10天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Intervals MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Remote MCP server for intervals.icu run data and analysis
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Powered by Cyan Eclipse Technologies — https://cetech.ai
The shared core of the Eclipse social adapter family — one canonical, owner-approved content package becomes a native draft, scheduled post, live post, or prep pack on each platform, according to what that platform actually sanctions. Analytics return with their platform definitions intact. It never uses a session workaround, never automates around a platform gate, and never publishes an unapproved variant.
Social platforms are separate publishing systems with separate accounts, media rules, API permissions, metrics, link behavior, and enforcement risk. A generic "post everywhere" abstraction that hides those differences produces broken crops, dead links, false analytics, and account jeopardy. The core holds the things every adapter must agree on — canonical content, rights, claims, approval, adaptation diffs, receipts, account safety — so each adapter only has to tell the truth about one platform. Spec: ~/workspace/cyan-eclipse/eclipse-social-family-spec-20261025.md (§3–§7).
v0.1.0, phase S0 core. Governance only: this server performs no platform action and makes no network calls. It holds packages, computes variants + diffs, records hash-bound approvals, evaluates engagement policy, and receipts everything. Adapters execute — or hand the owner a prep pack — elsewhere, only in their sanctioned mode. Local stdio, Python stdlib only, synthetic fixture package. No certification claimed — bench pending.
An approval binds hashes, not vibes (§3.1). Ingest issues a SHA-256 content hash over the canonical object; every variant gets a variant hash over its media, copy, link, order, disclosures, schedule, and destination. approve_variant records both hashes; approval_check recomputes them from current fields. Any change — copy, schedule, destination, link, disclosure — changes the hash and invalidates the approval; the variant returns to review. Proven three ways in the test suite, including a direct field-tamper case.
| Tool | What it does |
|---|---|
account_set | Register/update an authorized account: declared capability modes (capability → mode) + latest capability probe. A failed probe downgrades effective modes automatically — publish/draft collapse to PREP_PACK, own-engagement to COMMUNITY_PREP, reads stay flagged. Evaluation only; no credentials exist in this system. |
account_inventory | All accounts with declared + effective mode matrices, last probe, kill-switch state. |
content_ingest | Accept a canonical content object (§3.1): masters + provenance, copy, claims with sources, rights per asset, accessibility assets, disclosure record, intended/prohibited surfaces, schedule. Missing rights, unsourced claims, or missing alt text are named blockers. Re-ingesting changed content bumps the version. |
content_get | One canonical record in full. |
adapt_preview | Build one native variant for an adapter profile (aperture_feed, aperture_reel, aperture_story, prism_shorts, zephyr, wire): geometry, copy under the surface's limit, the surface's working link placement, platform-required disclosure labels, element order — plus the classified diff. |
adaptation_diff | The classified diff for a variant (MEDIA_CROP, TEXT_REWRITE, LINK_PLACEMENT, ORDER, DISCLOSURE, METADATA, FORMAT_OMISSION, …). A rewrite that drops a canonical number/claim is flagged substantive — never silent. |
variant_revise | Revise a variant; the hash recomputes and any approval bound to the old hash is invalidated. |
approval_pack | The review artifact: canonical item + variants + diffs + destinations + schedule. |
approve_variant / approval_check | Record / verify a hash-bound owner approval. |
policy_check | The engagement playbook as an evaluator (§5). Actions: like, comment, report_stop, reset. Enforces week-1 caps (≤15 likes, ≤5 comments/day), week-2+ caps (≤30/≤10), ≤2 likes per target per day, no links / no self-promo / no hashtag stuffing / ≤1 emoji in comments, no duplicate comments, and stop-signal finality (an action block stops the session until an owner reset). Every check is receipted, ALLOW and DENY alike. |
engagement_log / engagement_report | Append-only log of executed/owner-completed actions + the daily-report view (totals vs caps). No action goes unreported. |
adapter_kill_switch | Disable family / one adapter / one account. Writes freeze first; drafts and receipts remain readable. |
receipt_list | The hash-chained receipt ledger, with chain verification. |
PUBLISH_API · DRAFT_API · PREP_PACK · READ_API · OWN_ENGAGEMENT_API · COMMUNITY_PREP · COMMUNITY_API_PILOT. No mode includes browser-session scripting, cookie reuse, proxies, or password collection — ever (§7). Community engagement defaults to COMMUNITY_PREP for every adapter at launch.
python3 server.py # MCP over stdio, stdlib only, no dependencies
python3 smoke.py # end-to-end smoke over real stdio (temp state) python3 -m unittest discover tests # 26 tests
State persists in data/state.json beside the server (override with ECLIPSE_SOCIAL_CORE_STATE). data/ is gitignored.
fixtures/sample_content.json — one synthetic White-Report-style episode package (9:16 reel master + cover, a sourced claim, owned rights, alt text, AI-media disclosure) that the tests and smoke drive end to end.
A Cyan Eclipse Technologies product. The "Powered by Cyan Eclipse Technologies" attribution travels with it.