English Français العربية

Eclipse Aperture MCP

Registre officiel Marketing et ventes

The Instagram adapter, formalized: capability-declared, hash-bound native variants for Feed

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

PYPI package eclipse-aperture
Claude Code 
claude mcp add eclipse-aperture-mcp -- uvx eclipse-aperture==0.1.0
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "eclipse-aperture-mcp": {
            "command": "uvx",
            "args": [
                "eclipse-aperture==0.1.0"
            ]
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Eclipse Aperture MCP
  2. Why this exists
  3. Status — honest labels
  4. Tools (4)
  5. Native rules carried in code (§9)
  6. Run it
  7. Roadmap (per spec §21)
  8. License / attribution

Eclipse Aperture MCP

Powered by Cyan Eclipse Technologies — https://cetech.ai

Eclipse Aperture — the Instagram adapter: one approved package becomes native Feed, Carousel, Story, and Reel variants for a professional account, with publishing and analytics only through Meta's sanctioned Graph API surface.

Why this exists

The White Report already operates Instagram professionally through the house's existing sanctioned connector. S0 turns that working route into a capability-probed, hash-bound product surface instead of a collection of habits (spec §9, §18). Aperture is that surface: the capability declaration, the native variants, the preview the owner approves, and the receipts.

Status — honest labels

v0.1.0, phase S0 formalization. This server posts nothing and makes no live calls. The house's Instagram operation continues through its existing connector, outside this product; Aperture references that route and never duplicates it — there is no second token path, no session handling, and no credential material anywhere in this code. Local stdio, Python stdlib only. No certification claimed — bench pending.

Tools (4)

ToolWhat it does
capability_probeReturns the capability matrix from a static declaration fixture (dated 2026-10-25, [verify]-flagged): PUBLISH_API for publishing/drafts, READ_API for reads, OWN_ENGAGEMENT_API for own-media comments, COMMUNITY_PREP for community engagement — the §9 posture for eligible professional accounts, grade A subject to Meta app permissions, review, account role, and current Graph API version. simulate_probe_failure=true exercises the family downgrade rule: write modes collapse to prep — automatically, and never to a workaround.
variant_buildBuild one native variant from a canonical package: Feed 4:5, Carousel in narrative order (first card = hook, payoff before end card), Reel 9:16, Story 9:16 — with the working link path (profile link; Story link sticker — caption links are not clickable and are never the conversion path), the platform AI-media label carried on the variant, classified diffs vs canonical, and the variant hash.
preview_packThe exact native preview the owner approves: rendered geometry, caption, link path, safe-zone notes, hashtags, disclosures, order — plus diffs and the hashes an approval binds.
receipt_listThe append-only, hash-chained receipt ledger, with chain verification.

Native rules carried in code (§9)

  • Feed portrait 4:5 uses the grid better than square; landscape derivatives are shown, never center-cropped blindly.
  • Reels/Stories 9:16 with platform safe zones respected — text and evidence stay out of the top/bottom UI bands.
  • Hashtags are searchable metadata, not stuffing; the approved set appears in the diff.
  • Threads is not a separate product (§8): it rides as a sub-adapter inside this Meta family tooling when its gated modes are proven — no Threads listing or claim exists.

Run it

python3 server.py            # MCP over stdio, stdlib only, no dependencies
python3 smoke.py             # probe + Reel variant + preview over real stdio
python3 -m unittest discover tests   # 11 tests

State persists in data/state.json (override with ECLIPSE_APERTURE_STATE). data/ is gitignored. The capability fixture lives at fixtures/capability.json; the smoke drives the social core's sample_content.json package.

Roadmap (per spec §21)

  • Dated Meta terms/capability record replacing the static declaration → live ig_capability_probe.
  • ig_media_stage / ig_container_verify / ig_publish_receipt / ig_insights_read / ig_own_comment_queue — only against the sanctioned Graph surface, only for approved hash-bound packs, with publish read-back before any completion claim. Execution wiring stays on the house's existing route.

License / attribution

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

Questions fréquentes

Qu'est-ce que Eclipse Aperture MCP ?

The Instagram adapter, formalized: capability-declared, hash-bound native variants for Feed

Comment installer Eclipse Aperture MCP ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add eclipse-aperture-mcp -- uvx eclipse-aperture==0.1.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Eclipse Aperture MCP ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Eclipse Aperture MCP est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Eclipse Aperture MCP ?

Il est publié par CYAN-ECLIPSE-TECHNOLOGIES-LLC. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.