Eclipse Muster MCP

Eclipse Muster MCP

The Customer Graph core: one register of the people an account serves, with provenance on every

Developer Tools

About

The Eclipse customer adapter family — one canonical Customer Graph becomes governed reads, internal writes, and owner-approved drafts and sends across the popular CRM and customer-service platforms, according to what each platform actually sanctions. Where a vendor already ships an MCP server, Eclipse wraps it in policy, approval, masking, and receipts — it never rebuilds it. Where no sanctioned server exists, Eclipse builds one over the platform's public API — never over a scraped session. Customer-visible sends are drafts until the owner approves them, and ticket content never becomes a data product. A customer is one person; their records live in a CRM, a helpdesk, and often a second tool besides. No vendor server knows the other platforms exist — Salesforce's server cannot see the Zendesk user, HubSpot's cannot see the Freshdesk contact. Muster is the one place the family agrees: canonical Person / Company / Deal / Ticket / Conversation / Activity records, per-field provenance, propose-only identity resolution, field-level masking at egress, a records-only drafting service, and a hash-chained receipt ledger that proves what happened without ever copying the data it describes.

No reviews yet. Be the first to review!

Visit Website

eclipsebazaar.com

Details

Added
Nov 20, 2026
Directory
MCP Servers

MCP Server Details

Transport
stdio
Runtime
python
Version
0.1.1
PyPI package
eclipse-muster
Registry name
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/muster

Share this listing

Share: