Prospre
Log food, plan meals, fix the diary, build the grocery list and move macro targets in Prospre.
Description from the maker (original English)
An FPS feel checklist, measured from a timeline any game's probe can write
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
FEELLAB_OUTYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"feellab": {
"command": "uvx",
"args": [
"feellab-mcp"
],
"env": {
"FEELLAB_OUT": "your-value"
}
}
}
}Run this in your terminal
claude mcp add feellab --env FEELLAB_OUT=your-value -- uvx feellab-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"feellab": {
"command": "uvx",
"args": [
"feellab-mcp"
],
"env": {
"FEELLAB_OUT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"feellab": {
"type": "stdio",
"command": "uvx",
"args": [
"feellab-mcp"
],
"env": {
"FEELLAB_OUT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
FEELLAB_OUT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account hpdkhoa, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 23 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Prospre, RSS.com MCP by usefulapi, Castos MCP by usefulapi
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Log food, plan meals, fix the diary, build the grocery list and move macro targets in Prospre.
Read podcasts and episodes; create and edit episodes, chapters and transcripts in RSS.com.
Read podcasts and episodes; create and update episodes; manage private subscribers in Castos.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Feel Lab
An FPS feel checklist, measured: every interaction a player has, checked from what the game really did.
Game feel is what a player feels between pressing a key and seeing the world answer. A shot should flash, sound and kick on the same frame; a round striking a wall should throw dust, make a sound and leave a hole; a hit taken should jerk the view and show where it came from; a blast nearby should shake the screen more than one far away. When one answer is missing or late, the game feels floaty or cheap, and nobody can say why.
Feel Lab turns that into checks. Your game's probe plays standard scenes and writes a timeline: the camera every frame, and every sound, effect, mark and damage event with its time. Feel Lab measures latency, kick, shake, presence, match and smoothness from it, and judges each item of an 82-item checklist. It never runs your game: any engine can write the timeline (docs/TIMELINE.md).
| Group | Items | Measured from a timeline |
|---|---|---|
| A. Shooting (your own gun) | 19 | 9 |
| B. Hitting (your bullets land) | 15 | 6 |
| C. Getting hit (damage taken) | 9 | 4 |
| D. Movement and the body | 11 | 2 |
| E. Interacting with the world | 7 | 0 |
| F. Enemies (zombies) | 5 | 0 |
| G. Explosions, fire and the world | 5 | 1 |
| H. Sound mix | 4 | 0 |
| I. Screen and comfort | 4 | 0 |
| J. Smoothness (feel breaks when the frame does) | 3 | 1 |
Items no timeline can show (a colour-blind option, a reload cancel's timing) are left for a person, with what to look for. feellab checklist prints them all.
| Measure | Example |
|---|---|
| Latency | the shot's flash and sound on the shot's frame; the hit marker within 50 ms of the hit |
| Sync | the shot's sound within 45 ms of its flash (ITU-R BT.1359) |
| Kick | the camera turns at least 0.3 degrees on a burst and settles within 0.6 s |
| Shake | a blast 5 m away shakes the view; one 50 m away at least 3 times less |
| Presence | every impact has an effect, a sound and a mark; every round fired ejects a case |
| Rhythm | footsteps at walking cadence (about 100 steps a minute and up); the head bobs |
| Smoothness | no frame twice the median length round a shot or a blast |
Every rule names its source. A range from game practice rather than evidence is marked as an estimate.
pip install feellab-mcp
feellab demo demo feellab judge demo
The demo writes timelines for two made-up games: "Juicy" passes every measured item; "Bare" (a debug dot where a round lands, no shake, silent steps) fails 17.
src/feellab/data/scenes.json and write one timeline each (docs/TIMELINE.md). Wrap the calls that start sounds and effects so each is recorded with its time; note the moments with no sound or effect of their own (a shot, an impact, a hit marker, damage, a flinch)."tags": ["muzzle"]). Where your asset names do not say what a sound or effect is for, put a feel_rules.json beside the timelines: {"dry": "slidelock"} tells Feel Lab that a sound named after a slide lock is the click of an empty gun.feellab judge , or gate_rows for a gate.The first game to use it (ToangTown) found 52 failing cases on four guns: a debug dot where a round lands, no shake anywhere, no blood, no footsteps, a climb that never comes back, a stall on the first shot.
| Tool | What it does |
|---|---|
list_checklist | The checklist by group: what the player should get, measured or for a person. |
list_scenes | The standard scenes a probe plays. |
list_metrics | Every metric: scene, unit, rule and source. |
check_timeline | A timeline file against the contract. |
judge_folder | A folder of timelines judged: each item's values and verdict, and a Markdown report. |
gate_rows | The metrics as rows for a gate (Weapon Lab's row format). |
{"mcpServers": {"feellab": {"command": "feellab-mcp"}}}
FEELLAB_OUT is the only folder Feel Lab writes to (its reports); ~/.feellab by default.
Feel Lab was built for ToangTown, an Unreal 5.8 co-op zombie FPS, next to Weapon Lab (weaponlab-mcp), whose Gate can judge Feel Lab's rows as cases.
MIT