Lixversion Mcp
Give coding agents Lix-backed version control actions with verdicts, receipts, usage logs, and audit-ready JSON via a paid remote MCP.
Overview
Lix Agent Version Control MCP is a MCP server for the Build phase that exposes paid remote Lix versioning with verdicts, receipts, and audit-ready JSON for agents.
What is this MCP server?
- Paid remote Lix Agent Version Control MCP over streamable-http
- Structured verdicts, receipts, usage logs, and audit-ready JSON responses
- Bearer Authorization from the Lix product website
- Registry tags: lixversion, lix, remote-mcp, paid-mcp, agent-tools
- Version 1.0.0; open repo clauxel/lix-agent-version-control-mcp
- Registry version 1.0.0
- Remote URL lixversion.clauxel.com/mcp with Bearer header
- Repository: github.com/clauxel/lix-agent-version-control-mcp
What problem does it solve?
Agent prompts and tool configs drift across experiments because nothing versions them with the same receipts you expect from serious tooling.
Who is it for?
Solo builders iterating on agent setups who want Lix versioning with MCP-native receipts and logs.
Skip if: Teams that only need Git for application code and have no Lix or agent-artifact versioning practice.
What do I get? / Deliverables
After connect, Lix operations through MCP return verdicts, usage logs, and JSON you can use to track and audit agent version changes.
- Lix versioning actions invoked via MCP with verdict payloads
- Usage logs and receipts for agent version operations
- Audit-ready JSON suitable for later review or compliance notes
Recommended MCP Servers
Journey fit
Agent version control is a Build concern because it shapes how you iterate on prompts, tools, and agent configurations alongside code. Agent-tooling is the shelf: Lix targets versioned agent artifacts rather than generic app frontend or backend scaffolding.
How it compares
Lix agent-version MCP host, not a general git skill or local dotfiles manager.
Common Questions / FAQ
Who is Lix Agent Version Control MCP for?
Indie builders using MCP agents who rely on Lix to version agent-related assets and want structured verdicts and receipts.
When should I use Lix Agent Version Control MCP?
Use it during Build while changing agent tooling, prompts, or Lix-tracked configs and you need audit-ready JSON outputs.
How do I add Lix Agent Version Control MCP to my agent?
Add https://lixversion.clauxel.com/mcp as a streamable-http remote MCP server and supply a Bearer token from the Lix product website.