Tuning Engines - Governed AI Runtime

io.github.cerebrixos-orgPublished by GitHub account cerebrixos-orgv0.4.34Updated Oct 24, 2026

Govern model, agent, skill, and MCP workflows with policy, approvals, traces, and usage analytics.

Overview

AI-generated overview

Lets an assistant fine-tune and manage models, run evaluations, and inspect governed agent traces, policies, and approvals through the Tuning Engines platform.

What you can do
The bundled MCP server exposes 60+ tools for training jobs, models, datasets, evaluations, and inference usage, plus runtime governance: traces, policy decisions, approvals, interventions, outcomes, and compliance checks. It can submit fine-tuning jobs on a GitHub repo, estimate costs, monitor GPU usage, and export models to S3. Tenant administration tools manage non-secret registry metadata, team members, and policy dry-runs.
When to use it
Use it when you want an assistant to drive model fine-tuning, evaluation, and inference on the Tuning Engines platform, or to review governance artifacts such as traces, policy decisions, and approval requests. It is not needed for local coding tasks that do not touch that platform.
Requirements
Local Node.js runtime; the package is installed or run via npx. A Tuning Engines account and the TE_API_KEY environment variable are required, obtained by signing up or running the CLI auth login. Network access to the Tuning Engines API is needed, and desktop MCP clients only.
Before you install
TE_API_KEY is a required secret and grants access to the account. Training, evaluation, and inference consume paid credits, so cost estimates should be checked first. Many tools write or change data, including job submission and cancellation, model and dataset deletion, tenant resource changes, and team member removal; some write tools require an explicit registry-writes flag. The server deliberately refuses inference-key creation and raw secret fields, so those must be done through the CLI or…

Installation

In SourceWeft

  1. Open Tuning Engines - Governed AI Runtime in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.34LatestSep 16, 2026

Score

25% 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 days25 pts

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

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.