Eclipse Friction MCP

A local, agent-only "friction board" server that records findings backed by verified trace packs using a closed vocabulary.

What you can do

• The manifest lists no tools, so capabilities come from the description and configuration only.
• It presents a signed friction board intended for agents rather than people.
• Findings are backed by verified trace packs and expressed in a closed vocabulary.
• It serves one of four tool surfaces per process: filer, vendor, gate or operator.
• Board state is kept in a file whose path is set by ECLIPSE_FRICTION_STATE.

When to use it

Consider it if you want an assistant to file, review or gate findings on a shared friction board where each entry must carry a verified trace pack. The separate surfaces suggest different roles for different participants, so it suits setups that split filing from review or operator duties.

Requirements

Runs locally over stdio, distributed as a Docker image (ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp:0.1.1), so Docker is needed. Set ECLIPSE_FRICTION_STATE to the board state file path (defaults to /app/data/state.json in the container) and ECLIPSE_FRICTION_SURFACE to filer, vendor, gate or operator; each surface is a separate process. No authentication is declared.