Lixversion Mcp

com.clauxel.lixversionPublished by lixversion.clauxel.comOfficial publisherv1.0.0Updated Oct 24, 2026

A paid remote MCP for Lix, built to return verdicts, receipts, usage logs, and audit-ready JSON.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Paid hosted remote MCP that gives AI agents version control for product assets, with change sets, version comparison, merge approval and receipts.

What you can do
  • Create agent change sets for product assets
  • Compare Lix versions
  • Approve Lix merges
  • Export version receipts and audit-ready JSON
When to use it
For teams that want AI agents to make and track changes to product assets under version control, with approvals and exportable receipts for audit. Only worth adding if you already plan to use the paid Lix service.
Requirements
Remote Streamable HTTP endpoint at lixversion.clauxel.com; no local package. A paid plan chosen on the product website and a bearer token sent in the Authorization header. Network access to the hosted service.
Before you install
Paid service: a plan must be purchased before production calls. The bearer token is a credential and should be kept secret. Tools can create change sets and approve merges, which change version state, and usage is logged. The README states the public repository holds no production source code.

Installation

In SourceWeft

  1. Open Lixversion Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.clauxel.lixversion%2Flixversion-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lixversion": {
      "type": "http",
      "url": "https://lixversion.clauxel.com/mcp"
    }
  }
}

README

Lix Agent Version Control

Give AI agents version control for every product asset.

Lix Agent Version Control is a paid hosted remote MCP for Lix. It exposes Streamable HTTP tool calls, bearer-token access, public server-card metadata, usage logs, and receipt-oriented JSON for AI agent workflows.

Public Endpoints

Access

This is a paid hosted remote MCP. Production calls require a bearer token issued from the product website.

http
Authorization: Bearer <token>

Unauthenticated browser visits to /mcp return a clear JSON error instead of internal details.

Tools

  • create_agent_change_set
  • compare_lix_versions
  • approve_lix_merge
  • export_version_receipt

Quick Start

  1. Open the website and choose a plan.
  2. Create or request an API token.
  3. Add the endpoint to an MCP client that supports Streamable HTTP remote servers.
  4. Send JSON-RPC requests with the bearer token.

Useful Links

Status

This repository is a public documentation and directory-submission reference for the hosted service. It does not contain the private production source code.

Source: README.md at commit 069a1e3

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.