@venelx/mcp
Allows triggering and monitoring Android builds, including build status, logs, and artifacts, through the Venelx CI/CD platform.
Diagnoses GitHub repository access, reporting whether the configured token has valid access to connected repositories and surfacing reasons for failures.
Allows triggering and monitoring iOS builds, including build status, logs, and artifacts, through the Venelx CI/CD platform.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@venelx/mcp Trigger an iOS build for my project and show its status."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@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 loginOpens
app.venelx.comin your browser; approve access there and the token is saved to~/.venelx/mcp-token. The server picks it up automatically — noVENELX_TOKENenv var needed.Manual token — create one in the Venelx dashboard at Account → API tokens: https://app.venelx.com/account/tokens, then pass it as
VENELX_TOKEN(see Configuration below).
Token scopes
Scope | What it allows |
| All read-only tools (list projects, status, logs, artifacts, …) |
| Everything |
Tokens look like vx_.... Treat them like passwords — pass them via environment
variables, never commit them.
Related MCP server: GoCD MCP Server
Configuration
Environment variable | Required | Default | Description |
| no* | — | Personal API token ( |
| no |
| 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/mcpPin 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/mcpCursor
Add to .cursor/mcp.json:
{
"mcpServers": {
"venelx": {
"command": "npx",
"args": ["-y", "@venelx/mcp"],
"env": {
"VENELX_TOKEN": "vx_..."
}
}
}
}Kimi Code / generic MCP client
Same shape as above — add to your client's MCP JSON config:
{
"mcpServers": {
"venelx": {
"command": "npx",
"args": ["-y", "@venelx/mcp"],
"env": {
"VENELX_TOKEN": "vx_...",
"VENELX_API_URL": "https://api.venelx.com"
}
}
}
}Local development
git clone <repo> && cd venelx-mcp
npm install
npm run buildThen point your MCP client config at the local build:
{
"mcpServers": {
"venelx": {
"command": "node",
"args": ["/path/to/venelx-mcp/dist/index.js"],
"env": {
"VENELX_TOKEN": "vx_..."
}
}
}
}Tools
Tool | Scope needed | What it does |
| read | List projects the token can access (id, name, GitHub URL, platforms, role). |
| read | Project details plus a GitHub access summary. |
| write | Queue a build for a platform ( |
| read | Current pipeline status per platform + the 10 most recent builds. |
| read | Last N lines of a build log (latest build, or a given |
| read | Build artifacts for a project. |
| read | Build workers owned by the account (name, status, capabilities). |
| read | Code-signing readiness, optionally per platform ( |
| read | GitHub repo access diagnosis: |
| read | macOS only. List provisioning profiles ( |
| write | macOS only. Export the matching Distribution cert + key from Keychain and upload it with the best-matching local provisioning profile(s) as this project's iOS signing credentials. Only one extension bundle ID (e.g. a share extension) can be synced today — see Limitations below. |
| read | Scan a local project checkout's |
| write | Upload a local project checkout's release keystore as this project's Android signing credentials. |
| read | Build stack, build targets (with triggers), build commands per target, and project settings ( |
| write | Set |
| write | Replace the build steps of ONE target (others untouched). Commands are validated server-side; rejected ones are listed in the error. |
| write | Reset all build commands to the stack defaults. |
| write | Change the build stack ( |
| write | Add, edit or delete one build target (platform, profile, artifact type, PR/push triggers). Custom build commands are preserved. |
| read / write | Build environment variables (encrypted; values never returned). |
| read / write | App-test (Maestro) runs and configuration — partial updates merge into the stored config. |
| read / write | Playwright web-test sites. |
| read / write | Targets, no-code flows, schedule, triggers, notifications. Credentials are masked on read and kept when sent back masked. |
| write / read / write | Queue a web test, read results, accept screenshots as the visual baseline. |
| write | Upload gitignored files the build needs (google-services.json, keystore, local.properties, .env) from this machine; written into the build workspace before every target's build. |
| write | Secrets for repo-mode site builds; check a flow without saving. |
Onboarding and workers
Tool | Scope | What it does |
| read | Scan a local repo (read-only): GitHub URL, branch, stack, app folder, platforms, env var names, gitignored build files |
| write | Create a project linked to a GitHub repo and register the webhook |
| read | One-line worker install command (macOS/Linux/Windows) |
| read | CPU / memory / disk / queue history for a worker |
| read | Build minutes and builds per worker for a month |
| write | Assign a worker to a team (or clear it) |
Set up a project with one prompt
Paste this into your MCP client from the repo you want to build (also in the docs at https://docs.venelx.com/mcp):
Set up this repository on Venelx using the venelx MCP server. Run detect_project_setup and show me
the result, then create_project with the detected values, set env vars (ask me for values; never read
my .env), sync gitignored build files and signing only after I approve, make sure a worker is online
(worker_install_command if not), then trigger_build and follow the logs. Never print secrets.Local signing sync — limitations
iOS only supports one extra provisioning profile per project today (whichever sub-bundle-ID extension is found locally — typically a share extension). If your app has multiple extension targets (share extension and widget, for example), only one gets synced;
sync_local_ios_signing's response lists every extension bundle ID it found so you can see what was skipped. Supporting arbitrary extension counts needs a larger change to how Venelx stores iOS signing credentials — not done yet.sync_local_ios_signingexports every codesigning identity in your login Keychain into one.p12(macOS'ssecurity exportdoesn't cleanly filter to a single identity) and refuses to run at all if noDistributionidentity is present, since an AppStore/AdHoc profile without a matching Distribution cert+key can't actually sign a release build.
Troubleshooting
401 Authentication failed —
VENELX_TOKENis missing, wrong, or revoked. Create a new token at Account → API tokens (https://app.venelx.com/account/tokens) and update your MCP config.403 Forbidden on
trigger_build— your token only has thereadscope. Create a token with the write scope.Could not reach the Venelx API (ECONNREFUSED / ENOTFOUND) — the API base URL is unreachable. Check
VENELX_API_URL(defaults tohttps://api.venelx.com) and your network.Nothing happens / no output — MCP servers speak JSON-RPC on stdout; run it through your MCP client, not directly in a terminal. Diagnostics are printed to stderr.
License
MIT
Available Tools
9 toolsbuild_statusA
Get the current build pipeline status per platform plus the 10 most recent builds for a project.
Inputs: projectId (required).
get_projectA
Get full details for one Venelx project, including a summary of its GitHub access state.
Inputs: projectId (required).
github_accessB
Diagnose GitHub repository access for a project: githubAccess {ok, reason, message} and the githubAuth credential source label.
Inputs: projectId (required).
list_artifactsC
List build artifacts (installable binaries etc.) for a project.
Inputs: projectId (required).
list_projectsA
List all Venelx projects the API token can access (id, name, GitHub URL, platforms, role).
Inputs: no named parameters.
list_workersA
List the build workers owned by the current account (name, status, capabilities).
Inputs: no named parameters.
signing_statusB
Check code-signing readiness for a project. Optionally filter by platform ("ios" or "android").
Inputs: projectId (required), platform.
tail_logsA
Return the last N lines of a build log. If buildId is omitted, the most recent build of the project is used.
Inputs: projectId (required), lines, buildId.
trigger_buildA
Trigger a CI/CD build for a project on a platform (e.g. "ios" or "android"). Requires an API token with the write scope. Returns jobId/status/message; a skipped build includes a skipReason (e.g. signing_not_ready, github_token_invalid).
Inputs: platform (required), projectId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool targets a distinct operation: listing vs. fetching details, triggering builds vs. checking status, tailing logs, listing artifacts/workers, and checking signing/access readiness. There is no overlap between tools, so an agent can reliably select the right one.
Tools generally follow a verb_noun pattern (list_projects, get_project, trigger_build, tail_logs). A few status-oriented tools use noun-only names (build_status, signing_status, github_access), but the style is uniformly snake_case and predictable, with only minor deviation from the strict verb-first convention.
With 9 tools, the surface is well-scoped for a CI/CD and project management server. Each tool addresses a clear need (listing, detail, build, logs, artifacts, workers, readiness checks) without redundancy or bloat.
The core CI/CD lifecycle is covered: listing projects, getting details, triggering builds, checking status, fetching logs, and retrieving artifacts. Notable gaps include build cancellation and artifact download endpoints, but these are minor and likely handled externally; the main workflows are complete.
Maintenance
Related MCP Connectors
Inspect and control your Northflank projects, services, jobs, and builds from your AI assistant.
Plan Salesforce deploys, open pull requests and trigger pipelines from your AI client.
Trigger and inspect Codemagic CI builds, apps and artifacts.
Deploy and manage Jade Hosting projects from AI clients. Jade account and OAuth required.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with the Vercel REST API to manage projects, deployments, domains, environment variables, and teams through natural language commands.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query and manage GoCD pipelines, stages, and jobs through the Model Context Protocol. It allows users to trigger builds, analyze failures, and access build logs or artifacts using the GoCD REST API.2MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Jenkins CI/CD servers, including checking build status, triggering builds, and retrieving build logs.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to debug pipeline failures, analyze build logs, troubleshoot CI/CD configurations, and manage pipelines and repositories through the Model Context Protocol.MIT