Synqtune

com.synqtunePublished by synqtune.comv0.1.6Updated Nov 7, 2026

Fine-tune a small model on your data and benchmark it against your LLM API, in your AWS account.

VerifiedSTDIODesktop onlyCloud & InfrastructureAI & ML

Overview

AI-generated overview

Synqtune lets an assistant launch fine-tuning pipelines, track runs, evaluate models and compare them against an LLM, using your own AWS account.

What you can do
  • List task templates and the inputs and data formats each pipeline needs
  • List recent pipeline runs by status and inspect one run's step, progress, error and evaluation summary
  • List saved models with their latest and production versions
  • Re-evaluate a model version on a held-out S3 file, optionally against an LLM
  • Read the comparison report between a fine-tuned model and the LLM it should replace
  • Estimate GPU training cost and compare monthly LLM API spend with serving the model
When to use it
Useful when you want to fine-tune a small model on your own data and decide whether it can replace an LLM API call, and want an assistant to check runs, scores and cost trade-offs without leaving the chat.
Requirements
Runs as a local process (PyPI package synqtune-mcp, stdio transport) on a desktop machine. Needs a SYNQTUNE_API_TOKEN from Agent access in SynqTune, and optionally SYNQTUNE_URL, which defaults to the hosted SynqTune address. Training data and evaluation files live in S3 in your AWS account.
Before you install
The token is read-only unless it was created with Can launch runs; a launch-capable token can start training that spins up GPU instances billed to your AWS account. launch_pipeline returns only a plan and cost estimate unless confirm=true, so review the plan and cost with the user before confirming. Evaluation reads files from S3, and run and model details are sent to the SynqTune service.

Installation

In SourceWeft

  1. Open Synqtune 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.

Tools

8

list_templates

Task templates a pipeline can start from, with the inputs each needs and the data format it expects.

Takes no parameters.

list_runs

Recent pipeline runs, newest first. status: all, running, completed, failed or cancelled.

Parameterslimitstatus

get_run

Status of one run: current step, progress, error, and a summary of its evaluation and comparison.

Parametersrun_idrequired

get_comparison_report

The comparison between the fine-tuned model and the LLM it should replace: verdict (ready / close / not_ready), reasons, scores, the weakest labels or fields, and the examples where the fine-tuned model was worse.

Parametersrun_idrequired

list_models

Saved models with their latest and production versions.

Takes no parameters.

evaluate_model

Score a saved model version again on a held-out file in S3, optionally against an LLM. Nothing is trained. version_id: a model version (latest_version_id from list_models). eval_uri: .jsonl, .json or .parquet in the format the model was trained on, with rows it never trained on. Leave compare_* blank to compare with the LLM the training run compared with, if any. compare_system_prompt: the prompt the LLM gets in production; blank keeps the training run's, and with none the LLM is sent the task instruction. inference_engine: what serves the fine-tuned model in the comparison, huggingface or vllm (blank keeps the training run's); vllm also times the examples sent 8 and 32 at a time and needs a g5 instance or newer. Without confirm=true this only returns the plan and cost estimate: show it to the user and call again with confirm=true once they agree; it starts a GPU instance billed to the user's AWS account.

Parametersconfirmeval_urirequiredinstanceversion_idrequiredcompare_modelcompare_providerinference_enginecompare_max_samplescompare_system_prompt

estimate_cost

GPU cost of a training run (per hour, per day, rough total for the run) and, if you give current LLM usage and prices, the monthly API spend vs serving the model on the same GPU.

Parametersinstancetemplateinput_tokensoutput_tokenswith_comparisonmonthly_requestsprice_in_per_mtokprice_out_per_mtokserving_hours_per_day

launch_pipeline

Train a model from a task template on data in S3, in the user's AWS account. Without confirm=true this only returns the plan and cost estimate: show it to the user and call again with confirm=true once they agree. Launching starts GPU instances billed to the user's AWS account. inputs: the template's inputs (see list_templates), e.g. {"labels": "billing, refund, shipping"}. compare_*: optionally compare with the LLM the model should replace (provider anthropic, openai or gemini). The provider key must already be saved in SynqTune under Settings > LLM provider keys; keys are never passed here. holdout_uri: a held-out file (same format as the source) to test on instead of a random split of the source. compare_max_samples: how many held-out examples to send to the LLM (default 300). compare_price_input_per_mtok / compare_price_output_per_mtok: the LLM's USD price per 1M tokens, so the report shows its cost next to the fine-tuned model's. max_steps, batch_size, base_model: override the template's training. inference_engine: what serves the fine-tuned model in the comparison, huggingface (default) or vllm. vllm gives production-like speed and cost, also times requests sent 8 and 32 at a time, and needs a g5 instance or newer.

Parametersinputsconfirminstancerun_namerequiredtemplaterequiredmax_stepsbase_modelbatch_sizesource_urirequiredholdout_uricompare_modelcloud_account_id+6 more

Version history

2
  1. v0.1.6LatestNov 4, 2026
  2. v0.1.5Nov 1, 2026

Score

55% 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
  • 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • 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.