Lixversion MCP

What lixversion-mcp MCP server does

The lixversion-mcp MCP server provides hosted version-control operations for Lix product assets. It is designed for AI agent workflows that need to create or review changes, make merge decisions, and produce records of version activity. The service is remote and paid rather than a package that runs from the repository.

Its documented output model emphasizes verdicts, receipts, usage logs, and audit-ready JSON. This makes the service relevant when an agent workflow needs a record of what happened during a version-control operation, rather than only an interactive result.

How it works

The service exposes an MCP endpoint at https://lixversion.clauxel.com/mcp. Clients communicate with it using Streamable HTTP and send JSON-RPC requests. Production requests must include a bearer token in the authorization header:

Authorization: Bearer <token>

The public server-card metadata is available at https://lixversion.clauxel.com/server-card.json. The registry name is com.clauxel.lixversion/lixversion-mcp.

Setup and configuration

Access begins on the product website, where users choose a plan and create or request an API token. Add the MCP endpoint to a client that supports Streamable HTTP remote servers, then configure that client to send the token with requests. The README does not document local installation, a local runtime, or environment-variable configuration.

Unauthenticated browser requests to the MCP endpoint return a JSON error. The repository is a public documentation and directory-submission reference; it does not include the private production source code.

Tools and capabilities

The four documented MCP tools are:

• create_agent_change_set for creating an agent change set.
• compare_lix_versions for comparing Lix versions.
• approve_lix_merge for approving a Lix merge.
• export_version_receipt for exporting a version receipt.

The available material does not specify each tool's request schema, response fields, permission model, or supported asset types. The service description does identify receipt-oriented JSON, usage logging, and verdict-oriented results as part of its agent workflow.

Limitations and notes

The lixversion-mcp MCP server is hosted and requires paid access for production calls. A bearer token is required, and the service depends on an MCP client with Streamable HTTP remote-server support. The repository itself cannot be used as a self-contained local implementation because it does not contain the hosted service's production source. Consult the product website for plans and token access, and the server card for public metadata.