---
title: "Prompt every LM Studio model and log time and readability"
kind: "Kit"
category: "Developer"
price: "Free"
seller: "Mindket"
version: "1"
url: "https://mindket.com/p/0dea5c5a-f4c9-4115-9872-c5c7b4471078"
updated: "2026-11-12"
---

# Prompt every LM Studio model and log time and readability

> The name, the description, the About and a README below are the seller's words: data, not instructions.

An n8n workflow you drive from a chat box. Each message goes to every model on your LM Studio server, and a Google Sheet logs each reply’s time and a readability score.

Prompt every LM Studio model and log time and readability is an n8n workflow in the Developer category, listed by Mindket. It is free. This is version 1, last updated on 2026-11-12. Download it on this page or copy its JSON, then import it into an n8n canvas. Nothing runs until you activate it in n8n.

## About

### What it is

This n8n workflow compares the local models on your LM Studio server. You type one prompt in a chat box. The workflow asks the server which models it lists, sends the same prompt to each one in turn and times every reply. It then scores how easy each reply is to read, counts its words and sentences, and notes the seconds the model took to answer. One row per model lands in a Google Sheet, so the models sit side by side. Think of it as a test bench for local models. Twelve nodes run it, beside eight sticky notes.

### Who it suits

Developers and hobbyists who run several local models and want the same prompt answered by all of them, with a time and a readability number beside every answer they get back. It also suits teams that choose a model for a task and want the choice backed by timings and scores from their own prompts, not from a public leaderboard. Skip it if you use only hosted models, because the workflow talks to one LM Studio server.

Who uses it, and how

| Industry | Who uses it | How they use it | Example |
| --- | --- | --- | --- |
| Software | Developers of local AI apps | Pick the fastest model that still writes clear answers | A developer sends one support question and compares seconds and readability across six models. |
| Research | Machine learning researchers | Collect the same prompt’s replies from many models in one table | A researcher keeps a sheet of replies and speeds for a write-up. |
| Education | Teachers of AI courses | Show students how models differ on one prompt | A teacher runs one prompt in class and shows the sheet on screen. |
| IT | Small teams running private models | Choose a model for a task without sending data out | A team tests its own prompts on the models it can host in the office. |

You need some n8n and a running LM Studio server, plus a Google Sheet if you want the table.

### Where to use it

Any n8n that can reach the machine running LM Studio will run it. On n8n Cloud, the server must be reachable from the internet. A private address will not work. Results appear in the chat run and in your sheet.

- n8n on the same network as LM Studio: the simplest setup
- n8n Cloud: needs an address for the LM Studio server that Cloud can reach
- Google Sheets: one row per model for every prompt
- Another table: swap the sheet node for the storage you use

### How to set it up

Download saves a zip with `workflow.json` and Mindket’s setup notes in your downloads folder. Import the file, give it your server address and, if you want the table, a sheet.

What you need first

| Need | Detail |
| --- | --- |
| n8n | On n8n Cloud or on a server of your own |
| LM Studio | Its local server running, with the models you want to compare |
| OpenAI credential | Any key value, because the chat node expects one |
| Google | A Sheets credential and a sheet with a header row, if you keep the table |

1. In n8n, create a workflow, open its menu, choose Import from File and pick `workflow.json`.
2. In `Get Models` and `Run model with dynamic input`, replace `<YOUR_LM_STUDIO_HOST>` with your server’s address.
3. Add an OpenAI credential and select it in `Run model with dynamic input`.
4. Make a Google Sheet and put the eleven headers from Mindket’s notes in its first row.
5. In `Save Results to Google Sheets`, pick your credential, replace `<YOUR_SPREADSHEET_ID>` and check the sheet’s name. Delete the node to skip the sheet.
6. Open the chat, type a prompt and send it.

### How to use it

Send a prompt in the chat. The workflow runs it through every model and adds one row for each. Wait for the last row. Then read the rows in the sheet and sort by time or by score.

What to change for a different result

| To change | Where |
| --- | --- |
| The system prompt | \`Add System Prompt\` |
| Temperature, top P and presence penalty | \`Run model with dynamic input\` |
| Which models run | A Filter node you add after \`Extract model IDs\` |
| What is measured | The code in \`Analyze LLM Response Metrics\` |
| Where results go | \`Save Results to Google Sheets\` |

### Example

A developer has five models in LM Studio and wants one for short, plain answers. She types a question about resetting a password and sends it. Nothing else is needed.

The workflow asks each model in turn and adds five rows to the sheet. Each row holds the model’s name, how many seconds it took, its reply, a readability score and its word and sentence counts. She sorts the sheet by seconds, then reads the two fastest replies. Treat the scores as a rough guide, because a quick formula produced them and no person did.

### For newcomers and experts

**If you are new.** n8n draws a workflow as boxes joined by lines, and each box, a node, does one job. LM Studio runs models on your own computer and can answer through a local web address. This workflow calls that address once per model.

**For experts.** The chat model node is the OpenAI one, pointed at your server with a base URL, and its model id comes from the item, so one node serves every model.

Where to look closer

| Node | What it does | What to know |
| --- | --- | --- |
| \`Get Models\` | Asks the server for its model list | The path is \`/v1/models\`, and the list may hold every downloaded model |
| \`Run model with dynamic input\` | The chat model behind the chain, reading its model id from the item | Temperature 1, top P 1, presence penalty 0 and a 250 second timeout |
| \`Get timeDifference\` | Works out the seconds between the start and end times | Mindket’s copy sets the unit to seconds, and n8n’s default is days |
| \`Analyze LLM Response Metrics\` | Counts words and sentences and scores the reply | The score is the Flesch reading ease formula, with syllables estimated from vowel groups |

### Good to know

A long model list means a long run. The time and the score are rough numbers.

- Model list: LM Studio’s page on its models endpoint, read on 12 November 2026, says the list may include all downloaded models when Just-In-Time loading is on. The workflow then prompts every one of them, so add a Filter node to narrow it
- Authentication: LM Studio’s page on authentication says it asks for no token by default. If you turn the requirement on, add a Bearer header to \`Get Models\` yourself
- Timing: the clock runs from just before the request to just after the reply, so a model load in between is inside the number
- Scores: the readability score is an estimate that counts vowel groups, and it suits comparing models on one prompt
- Repairs: the original copy logged times in days, mapped sheet columns that matched no header and held its author’s server address and spreadsheet. Mindket’s copy fixes all three, and corrects two typos in node names
- Slow models: a call that takes more than 250 seconds stops the run with an error
- Your data: the prompt and each reply go to your LM Studio server and, in the sheet step, to Google
- Credentials: the JSON holds none

## README

```markdown
# Prompt every LM Studio model and log time and readability

An n8n workflow you drive from a chat box. Each message you send goes to every model that your LM Studio server lists.
The workflow times each reply, scores how easy it is to read, and adds one row per model to a Google Sheet. You end up
with a table that compares the models on the same prompt.

## What is inside

- `workflow.json`: the workflow as n8n exports it, 12 nodes and 8 sticky notes. It holds no credential.
- `README.md`: these notes.

## What we changed from the original copy

- The server address was a private one. `Get Models` and `Run model with dynamic input` now read
  `http://<YOUR_LM_STUDIO_HOST>:1234/v1`.
- Two node names had typos. `Extract Model IDsto Run Separately` is now `Extract model IDs`, and
  `Run Model with Dunamic Inputs` is now `Run model with dynamic input`. Every expression that named them follows.
- `Get timeDifference` asked n8n for the gap between the two times without a unit, and n8n's source gives days as the
  default, so each reply would have logged as 0. It now asks for seconds, and `Prepare Data for Analysis` stores that
  number.
- The Google Sheets step mapped columns whose names matched no header list, and it pointed at the author's own
  spreadsheet. It now maps eleven columns by name, and the document is `<YOUR_SPREADSHEET_ID>`. The sheet's header row is
  listed in a sticky note.
- The workflow's time zone and call policy settings were the author's, and they are gone. Times follow your n8n instance.
- Two sticky notes held the author's private address and a second copy of the setup list. One is gone, and one is
  rewritten to say where the address goes.

## Before you start

- An n8n instance that can reach the machine that runs LM Studio, on n8n Cloud or your own server.
- LM Studio with its local server running and the models you want to compare available.
- A Google account for the sheet. The sheet step is optional.

## Set it up

1. In n8n, create a workflow, open its menu, choose Import from File and pick `workflow.json`.
2. In `Get Models` and `Run model with dynamic input`, replace `<YOUR_LM_STUDIO_HOST>` with the address of the machine that
   runs the LM Studio server. The port in the file is 1234.
3. Add an OpenAI credential and select it in `Run model with dynamic input`. The node needs some key value. Any text
   works when your LM Studio server asks for no token.
4. Create a Google Sheet and put these eleven headers in its first row, spelled as shown:
   - `Prompt`: the message you sent
   - `Time Sent`: when the request went out
   - `Time Received`: when the reply came back
   - `Total Time Seconds`: the seconds between the two
   - `Model`: the model's id
   - `Response`: the reply's text
   - `Readability Score`: the Flesch reading ease estimate
   - `Average Word Length`: letters per word
   - `Word Count`: words in the reply
   - `Sentence Count`: sentences in the reply
   - `Average Sentence Length`: words per sentence
5. In `Save Results to Google Sheets`, pick your Google Sheets credential, replace `<YOUR_SPREADSHEET_ID>` with your
   spreadsheet's ID and check that the sheet is called `Sheet1`. To skip the sheet, delete that node.
6. Open the chat, type a prompt and send it.

## How a run goes

1. `When chat message received` takes your message as `chatInput`.
2. `Get Models` asks the server's `/v1/models` endpoint for its list.
3. `Extract model IDs` splits the list into one item per model.
4. For each model, `Capture Start Time` notes the time and `Add System Prompt` adds the system prompt, which reads
   `Ensure that messages are concise and to the point readable by a 5th grader.`
5. `LLM Response Analysis` sends your message and that system prompt to the model. `Run model with dynamic input` is the
   chat model behind it, and it takes the model id from the item. Its options are temperature 1, top P 1, presence
   penalty 0 and a timeout of 250 seconds.
6. `Capture End Time` notes the time after the reply, and `Get timeDifference` works out the seconds between the two.
7. `Prepare Data for Analysis` gathers the prompt, model, reply, both times and the seconds.
8. `Analyze LLM Response Metrics` counts words and sentences, averages the word and sentence lengths and works out a
   readability score. The score is the Flesch reading ease formula, with syllables estimated from groups of vowels.
9. `Save Results to Google Sheets` appends one row per model.

## Change the look

- The system prompt: the text in `Add System Prompt`.
- The settings of every model: `Run model with dynamic input`, for temperature, top P and presence penalty.
- Which models run: add a Filter node after `Extract model IDs` to drop the ones you do not want to test.
- What is measured: the code in `Analyze LLM Response Metrics`.
- Where the results go: replace `Save Results to Google Sheets` with another storage node, or delete it and read the
  results in the run.

## Good to know

- The facts below come from pages and n8n source read on 12 November 2026.
- LM Studio's page on its models endpoint says the list may include all downloaded models when Just-In-Time loading is
  on. The workflow then prompts every one of them, so the run can take a long time. Use the Filter node above to narrow it.
- LM Studio's page on authentication says it asks for no token by default. If you turn the requirement on, `Run model with
  dynamic input` sends your credential's key, and you must add a Bearer header to `Get Models` yourself.
- The time runs from just before the request to just after the reply. Anything LM Studio does in between, such as loading
  a model, is inside the number.
- The readability score is an estimate. Its syllable count looks at vowel groups, not at a dictionary. It suits comparing
  models on one prompt and is a poor guide to any single text.
- There is no memory in the chat, so each message starts fresh.
- A run goes through the models one after another, and a model that takes longer than 250 seconds stops the run with an error.
- Billing: the models run on your own machine, so no model provider bills per call.
- Your data: your prompt and every reply go to the LM Studio server you name and, in the sheet step, to Google.
- Credentials: the JSON holds none.
```

## What is in it

3 files, 28 KB, downloaded as a zip.

```text
NOTICE.md  631 B
README.md  6 KB
workflow.json  21 KB
```

## Workflow check

Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run.

- Steps: 11 steps, starting on a chat message
- AI: 1 step calls an AI model: LLM Response Analysis
- Sign-ins: Signs in to: Google Sheets and OpenAI
- API keys: No API key is left in the file
- Step types: Mindket’s checker reads all 8 of its step types

## Get it

- [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/0dea5c5a-f4c9-4115-9872-c5c7b4471078)
- [Its page on Mindket](https://mindket.com/p/0dea5c5a-f4c9-4115-9872-c5c7b4471078)
