Eclipse Connect MCP
The MCP face of the hosted OAuth bridge — agents upload to YouTube through a human-granted, revocable key, never raw OAuth.
status: dogfoodclass: mcpPublishing
Vendor: Cyan Eclipse Technologies
What it does
- MCP facade over the Eclipse Connect relay: connect account, grant status, upload video, publish video, revoke grant — 5 tools over stdio
- Agents act through a revocable agent key, never raw OAuth tokens; the relay holds the grant
- Review-first enforced in the facade before any network call, and again at the relay: going public requires an explicit human approval flag
- The facade passes relay state through verbatim; it invents no status of its own
- Distinct bench surface from the relay: this facade is CERTIFIED(dogfood-facade); the relay (catalog: eclipse-connect) holds its own CERTIFIED(dogfood)
Tools
connect_account · grant_status · upload_video · publish_video · revoke_grant
Platforms
- MCP over stdio
Certification
Bench verdict: CERTIFIED(dogfood-facade)
Certified scope: CERTIFIED(dogfood-facade) — Eclipse Bazaar Test Bench 2026-10-25, 14/15 checks pass, 1 na (U1 auth: vault surrogate stubbed). Run by W-003 (Verity), suites/connectfacade.py. Facade only — the relay holds its own CERTIFIED(dogfood) card (eclipse-connect).
Not tested:
- Live relay / YouTube calls — transport stubbed at server.send (the product's single network seam); no live call made or claimed
- Vault surrogate credential attachment inside the real send() — stubbed out in this bench, not exercised
Bench scorecard (evidence): https://eclipsebazaar.com/cards/eclipse-connect-mcp-2026-10-25.json
Pricing
Free — v0.1.0 dogfood; hosted tier planned
Install / verify
docker run -i ghcr.io/cyan-eclipse-technologies-llc/eclipse-connect-mcp:latest
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).