Eclipse Social Core MCP

Name: Eclipse Social Core MCP
Author: CYAN-ECLIPSE-TECHNOLOGIES-LLC

by CYAN-ECLIPSE-TECHNOLOGIES-LLCversion 0.1.1i★ –iRuns on your computer

Registry nameio.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/social-core

Install

Overview

Description from the maker (original English)

One canonical, hash-bound package behind every Eclipse social adapter. It publishes nothing itself

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "social-core": {
      "command": "uvx",
      "args": [
        "eclipse-social-core"
      ]
    }
  }
}

Run this in your terminal

claude mcp add social-core -- uvx eclipse-social-core

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "social-core": {
      "command": "uvx",
      "args": [
        "eclipse-social-core"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "social-core": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "eclipse-social-core"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLC, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32589 servers in this category
Published to the registry more recently than 77% of the other 32589 servers in this category
Basic checks equal to or better than 100% of the other 32589 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Eclipse Social Core MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 10 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Detailing Manager

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Detailing Manager

by RadoslavMoshev

Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Eclipse Social Core MCP

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.

Why this exists

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).

Status — honest labels

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.

The hash law

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.

Tools (15)

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.

Modes (§2.1)

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.

Run it

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

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.

Roadmap (per spec §21)

S1 — Prism product face over Eclipse Connect rails.
S2 — Zephyr (built alongside this core) + Commons.
S3/S4 — Wire, Meridian, Pulse, Comet, Atlas by gate state. Each phase starts from a dated terms/capability record; a phase never inherits another adapter's verdict.

License / attribution

A Cyan Eclipse Technologies product. The "Powered by Cyan Eclipse Technologies" attribution travels with it.

Eclipse Social Core MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Detailing Manager

README from the maker

Eclipse Social Core MCP

Why this exists

Status — honest labels

The hash law

Tools (15)

Modes (§2.1)

Run it

Fixtures

Roadmap (per spec §21)

License / attribution