venelx/mcp

Developer tools

Эта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал

0 stars 0 forks Качество 71 Тренд 14

Repository Install

Venelx MCP server — let AI assistants set up and operate Venelx CI/CD pipelines (npx @venelx/mcp).

Обзор

An MCP (Model Context Protocol) server that lets AI assistants (Claude Code, Cursor, Kimi Code, and any MCP-compatible client) operate the through its REST API: list projects, trigger builds, check build status, tail logs, list artifacts and workers, and diagnose signing / GitHub access. The server talks to the Venelx API over HTTPS and to your AI client over . - - A with at least one project - A token — either of: - Opens app.venelx.com in your browser; approve access there and the token is saved to ~/.venelx/mcp-token. The server picks it up automatically — no VENELX_TOKEN env var needed. - — create one in the Venelx dashboard at : https://app.venelx.com/account/tokens, then pass it as VENELX_TOKEN (see Configuration below). Tokens look like vx_.... Treat them like passwords — pass them via environment variables, never commit them.

README

Показан фрагмент оригинального README. Открыть оригинал.

@venelx/mcp

An MCP (Model Context Protocol) server that lets AI assistants (Claude Code, Cursor, Kimi Code, and any MCP-compatible client) operate the Venelx CI/CD platform through its REST API: list projects, trigger builds, check build status, tail logs, list artifacts and workers, and diagnose signing / GitHub access.

The server talks to the Venelx API over HTTPS and to your AI client over stdio.

Prerequisites

Node.js ≥ 18
A Venelx account with at least one project
A token — either of:
- Browser login (recommended, no copy-pasting):
```
npx @venelx/mcp login
```
  Opens app.venelx.com in your browser; approve access there and the token is saved to ~/.venelx/mcp-token. The server picks it up automatically — no VENELX_TOKEN env var needed.
- Manual token — create one in the Venelx dashboard at Account → API tokens: , then pass it as VENELX_TOKEN (see Configuration below).

Token scopes

Scope	What it allows
`read`	All read-only tools (list projects, status, logs, artifacts, …)
`write`	Everything `read` allows, plus every tool that changes something: builds, web-test runs, build/test configuration, env vars, signing uploads. The API rejects any non-GET request from a read-only token. `npx @venelx/mcp login` issues a read-only token — create a read + write token at Account → API tokens for the configuration tools.

Tokens look like vx_.... Treat them like passwords — pass them via environment variables, never commit them.

Configuration

Environment variable	Required	Default	Description
`VENELX_TOKEN`	no*	—	Personal API token (`vx_...`). *Not needed if you’ve run `npx @venelx/mcp login` — falls back to `~/.venelx/mcp-token`.
`VENELX_API_URL`	no	`https://api.venelx.com`	API base URL (self-hosted etc.)

Install & run

Straight from GitHub (latest source, no npm release needed)

npx can run the server directly from the VenelX/mcp repo — npm clones it and builds it (prepare) on first run:

claude mcp add venelx -e VENELX_TOKEN=vx_... -- npx -y github:VenelX/mcp

Pin a release with a tag (github:VenelX/mcp#v0.1.2); without one you get main.

Claude Code

claude mcp add venelx --env VENELX_TOKEN=vx_... -- npx -y @venelx/mcp

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "venelx": {
      "command": "npx",
      "args": ["-y", "@venelx/mcp"],
      "env": {
        "VENELX_TOKEN": "vx_..."
      }
    }
  }
}

Открыть полный README на GitHub

Установка

npx -y @venelx/mcp

Новичок в MCP? Начните с руководства на mcpskill.org →

Конфигурация

{
  "mcpServers": {
    "venelx": {
      "command": "npx",
      "args": ["-y", "@venelx/mcp"],
      "env": {
        "VENELX_TOKEN": "vx_..."
      }
    }
  }
}