What it does
Qompass SFW game maker MCP: authoring and project state for SFW games, with a live lane gate.
- Connects –
- Account or key No key needed
- Category Games, sports, food & learning
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Claude cannot connect Meister yet
The maker has not listed install details in the MCP Registry yet
ChatGPT cannot connect Meister yet
The maker has not listed install details in the MCP Registry yet
What you can do instead
B · Others in Games, sports, food & learning that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- ShipSwift✓ ChatGPT
- LearnHouse✓ ChatGPT
- Anime Garden✓ ChatGPT
Claude Code cannot connect Meister yet
The maker has not listed install details in the MCP Registry yet
Cursor cannot connect Meister yet
The maker has not listed install details in the MCP Registry yet
VS Code cannot connect Meister yet
The maker has not listed install details in the MCP Registry yet
At a glance
- Downloads per weeki
- Not on npm/PyPI
- Verified domain
- ✓ qompass.ai
- Connection
- –
- Latest versioni
- 0.5.0
- Categoryi
- Games, sports, food & learning
- Published to registryi
- Nov 18, 2026
- Code last changedi
- Nov 19, 2026
- Maker
- qompassai
- Website
- qompass.ai
- Registry status
- Active
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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 20, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain qompass.ai (the registry checks domain ownership)
- ✓ Pass
Still maintained
Code last changed yesterday
- ✓ Pass
Has a licence
Uses Apache-2.0
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/qompass-meister)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Games, sports, food & learningi
- More stars than 0% of the other 1623 servers in this category
- Published to the registry more recently than 94% of the other 1623 servers in this category
- Basic checks equal to or better than 99% of the other 1623 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Meister safe?
It passed 3 of 3 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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
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).
Is it still maintained?
The GitHub repo last changed yesterday, and the latest version (0.5.0) reached the registry 2 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.
What can I use instead?
In the same category: Anime Garden, WilmAI, Lumify Sports Intelligence, Savecraft, GoodWatch
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
WilmAI
Finland's Wilma school system for parents and students: schedule, homework, exams and messages.
Lumify Sports Intelligence
Schedules, scores, odds, splits & explainable AI bet confidence — 8+ sports, free instant key.
Savecraft
Savecraft serves real save game data and expert game knowledge to AI assistants.
GoodWatch
Find movies and TV shows, track watches, and get suggestions based on your taste.
| This one Meister | Anime Garden | WilmAI | Lumify Sports Intelligence | Savecraft | GoodWatch | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | Yes | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 3/3 | 4/4 | 3/4 | 4/4 |
| License | Apache-2.0 | AGPL-3.0 | MIT | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
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.
Meister — Qompass SFW game maker MCP
Commissioned by the Owner, 2026-11-16 (decision D-1604), as the plan of record for building Meister to 1.0. Name ruled by the Owner, 2026-11-16 (decision D-1603): Meister — the guild master, the rank earned by submitting a masterwork. Its own ancestor *magister* was the runner-up.
Meister is the SFW counterpart to Ardor, the NTRanch lane's NSFW maker MCP. The pair share a spine and a shape — one maker surface per lane — and nothing else crosses: no content, no records, no canon. Ardor makes games of passion; Meister makes games of craft.
Purpose
One Qompass-lane maker surface for building SFW games end to end: the teaching games (Niflheim, Versemend), the puzzle line (light-show), narrative games, and every future Qompass title. Meister is an authoring and project-state server. It is not a runtime or orchestration replacement for phlow, not a media engine (that is lumen), and not a publishing surface (that is slipway).
The worked examples already exist. Niflheim and Versemend were built by hand through the process this server formalises: decisions became gated, deterministic production. Meister exists to make that way of working the default for every SFW title — scaffold, canon, authored content, media, playtest, and release handoff, all as structured game data with provenance, all reproducible.
Why a server
Meister holds authored project state across sessions and enforces canon and lane decisions through a decide()-class gate before canonical writes. State plus enforcement meets the estate's server graduation rule; thin one-shot capabilities remain skills. The SFW content pipes currently homed in lumen as tooling and gate scripts (genesis, canon census, keeper chains) are Meister's seed: the three graduation candidates named in the lumen pipes definitions move server-side here, on the demonstrated enforcement need this commission records. Everything else in lumen stays in lumen — Meister routes media work to it and records the handoff.
Technology contract
- Rust server on rmcp, MCP modern era only (2026-07-28), stateless/discover-first, per the fleet standardisation ruling.
- Tiger Style MCP discipline: bounded tool surface, complete schemas, annotations from birth, explicit error, timeout, and security contracts; the tool surface stays inside the fleet EFLO token budget or carries a gated waiver with evidence.
- Kotlin MCP SDK companion for Android-side authoring, preview, and playtest bridges, following the established fleet pattern; Android-facing pieces are feature-gated and compiled out of release/store artifacts unless explicitly enabled.
- Pure Rust core where it owns game data and project state; edition 2024 and the estate nightly pin apply to Rust game code.
- A TUI of fleet-standard capability is part of the 1.0 surface, per the fleet TUI programme: plan/auto modes, live progress, media preview at the highest fidelity the terminal stack allows.
- No containers anywhere in the build or deployment path. Local validation only; the estate runs no CI by design.
Lane law (never softened)
- Every record Meister creates carries
origin_lane: qompassandcontent_label: sfwfrom birth, with evidence. Meister is a Qompass-lane system; its records are born classified, never classified after the fact. - Intake accepts only
content_label: sfw. NSFW input is refused with a typedlane_mismatch; missing or other labels are refused aslane_unclassified. Unclassified defaults to the NSFW side — fail closed. Refusals are typed, name the offending ids, and happen before any mutation: a refused run leaves inputs byte-identical. - Nothing NSFW is authored, stored, or processed in a Qompass tree. Content questions that arrive unclassified are refused, never investigated by processing them.
- No tool declares a visual or audio PASS. Measurements are floors; the Owner's eye and ear are the verdict, recorded through numbered verdict packs. A pipeline stage that cannot produce its gate evidence has not happened.
The spine
Every Meister pipeline is the lumen content-factory spine applied to one kind of state:
Describe → Propose → Freeze → Emit → Prove
- Describe — the canon record is written first. Generation against an unwritten record is forbidden.
- Propose — a candidate is produced against the record. A proposal is not an asset; it is born
candidateand stays quarantined from canon. - Freeze — adoption is a ruling, not a side effect. Canon is adopted or changed only by the Owner's ruling on a numbered verdict pack; the freeze pins a hash.
- Emit — named, versioned, deterministic emitters turn frozen records into engine-ready artifacts. Same record in, byte- identical artifacts out.
- Prove — every stage leaves a conformance run record with its gate evidence, or it did not happen. Numbers in a gate report cite their run artifacts; an unverifiable number routes to REVIEW, never to PASS.
Tool groups
The surface mirrors Ardor's ten groups, re-homed to the SFW lane. Group numbers match Ardor's deliberately, so the pair can be read side by side; where a group's content is lane-specific, the SFW form is specified here and the NSFW form stays in Ardor, unshared.
- Project scaffolding — create and inspect Qompass game projects with the estate conventions already in place: engine shell (Bevy first; Godot, Ren'Py, Unity, and Unreal targets as emitter profiles), metadata, test layout, lane stamps, and the project's genre pipeline pack (below) selected at birth.
- Cast and canon — character identity records, identity locks (silhouette, palette, face and body proportions, thumbnail recognisability), appearance and rig references, canon checks, and versioned changes to cast data. A character is identity- locked at intake, before any detail work — the lock is a hard gate, not a style preference.
- Scenes and systems authoring — dialogue and scene graphs, schedules, flags, progression DAGs, economies, state machines, and minigame definitions: the game-systems authoring verbs every genre pack builds on.
- Dialogue and narrative creation — author dialogue as structured game data, not loose prose: lines, speakers, choices, conditions, per-character reaction profiles driven by relationship state, prior choices, and scene history; prerequisites and continuity effects; branching; and cues for animation, voice, and sound. Expression is whole-body: a reaction record names posture, gesture, and stance, not only a face. This is Ardor group 4's SFW form — the adult state machinery (arousal, conditioning, kink actions, haptics) does not exist here and is never imported.
- Story, plot, and level making — create and validate story arcs, beats, quests and objectives, character arcs, relationship progression, branching endings, scenes, encounters, and levels. Level tools cover layout and scene composition, triggers, schedules, progression gates, minigame placement, and deterministic playtest generation from the authored graph.
- Content standards and accessibility — first-class scaffolding and checks, never progression-gated: content tags and rating metadata (ESRB, PEGI, IARC), age-appropriateness review records, accessibility surfaces (photosafety — flash and transition-rate gates are hard limits, not options; colour- vision-safe palettes; remappable input; subtitle and text- scaling contracts), and plain-language summaries of what a game contains. Where Ardor scaffolds safety for adults, Meister scaffolds appropriateness for everyone, including classrooms.
- Asset routing and provenance — intake, hash, provenance, and routing records for every media artifact a project uses. Specialist work stays with its owner (see the media map below): lumen for media conversion and the sprite-to-3D factory, eigenstyle for voice style, bloch for lessons, fathom for clean-room study of existing games. Meister calls or records handoffs; it re-implements nothing.
- Playtest and QA — scripted playthrough definitions, deterministic replay and hash checks, screenshot specifications for verdict packs, and defect records tied to authored project state. Test design follows the estate split: half validation, half adversarial, by construction.
- Build and release handoff — prepare channel artifacts and hand them to slipway for Play and F-Droid certification, and to the channel executors below. Meister never forks slipway's publish gates or definitions. This group carries a channel-target registry for SFW distribution: Google Play (the SFW lane's home channel; adult content is prohibited platform-wide, which is why this registry is Meister's and not Ardor's), F-Droid, itch.io (pipeline via butler; desktop, web, and Android artifacts), Steam, GOG, Epic Games Store, Humble, Apple App Store, Microsoft Store, console portals (Nintendo, PlayStation, Xbox — curated-pitch class), and direct web release (own site, GitHub releases). Each target records platforms, content-policy notes, automation class (pipeline / prepared-submission / curated-pitch), artifact requirements, and its handoff executor. Every channel is verified live at build time; a channel that fails verification is flagged with evidence, never given invented requirements. Whether the estate ships on a given channel for a given title remains the Owner's per-title decision; the registry records capability, not intent.
- Channel credentials and sessions — auth, API key, token, and login management for every channel in the group-9 registry, under Ardor group 10's hard rule, adopted verbatim: Meister manages credential references and status, never values. No tool stores a raw secret in project state, returns one in its output, or writes one to a log or report. A channel-account record holds the channel, the account identity, the credential kind, where the value lives (a primo
passpath or a Secure Vault entry), scopes, expiry, and last-verified time. Tools register and inspect channel accounts, run per-channel verification probes where the channel supports one, track expiry and rotation, and run a publish preflight that refuses a handoff when the target channel's auth is missing or unverified. Channels with no API get honest login-reference records, never invented token flows.
The media map — what lumen provides
Meister authors game data; lumen is the estate's deterministic media-conversion engine, and every media artifact in a Meister project is produced or converted through lumen's formats and recorded in group 7. The applicable lumen media surface:
- 2D stills — sprites, sprite sheets, tilesets, character portraits and whole-body expression portraits, backgrounds, key art, UI art. PNG canonical; Aseprite-native pipelines for pixel work; every still carries its keeper chain (governing reference, candidate history, gate reference) from birth.
- Pixel art — Aseprite
.asepritesources, deterministic batch exports, palette discipline, sprite-sheet packing. - Animation — sprite animation strips and GIF assembly; idle/breathe cycles and companion idle strips; and the estate's shipped-animation form: code-as-animation. A frozen, hashed scene spec compiles through a timeline compiler to rig/curve data and renders deterministically — double-rendered byte-identical. Diffusion image-to-video is reference only and never ships.
- 3D — lumen's parametric sprite-to-3D factory: a 2D sprite is identity-locked, projected onto the canonical rigged base (Mixamo-compatible skeleton, morph-target expression set), and exported glTF/GLB-first, with