Qué hace
Qompass SFW game maker MCP: authoring and project state for SFW games, with a live lane gate.
Texto original del autor
- Conexión –
- Cuenta o clave No necesita clave
- Categoría Juegos, deportes, comida y aprendizaje
Por qué está en este puesto
Las listas se ordenan por una puntuación de uso (sobre 100) con estas partes
| Popularidad | 0/80 | Estrellas de GitHub o descargas semanales: la mayor cuenta 60, la menor 20 |
|---|---|---|
| Actualidad | 12/12 | Puntuación completa con una versión o cambio de código en 30 días |
| Sigue respondiendo | 0/8 | El endpoint en la nube respondió en la última revisión |
| Puntuación de uso | 12/100 |
Calidad: Pasó 3/3 revisiones básicas (se muestra, no ordena) · Impulso: Sin datos aún (Solo se usa en la pestaña En auge)
Instalación
Elige la app de IA que usas y copia la configuración.
Pasó 3/3 revisiones · Funciona en tu computadora
Primero: ¿qué IA usas?
Elige tu app y los pasos aparecen abajo.
Claude todavía no puede conectar Meister
El autor aún no ha puesto cómo instalarlo en el registro MCP
ChatGPT todavía no puede conectar Meister
El autor aún no ha puesto cómo instalarlo en el registro MCP
Lo que puedes hacer en su lugar
B · Otros en Juegos, deportes, comida y aprendizaje que funcionan con ChatGPT
Elegidos entre los más usados de la misma categoría, solo los que se conectan con una dirección y sin clave
- ShipSwift✓ ChatGPT
- LearnHouse✓ ChatGPT
- Anime Garden✓ ChatGPT
Claude Code todavía no puede conectar Meister
El autor aún no ha puesto cómo instalarlo en el registro MCP
Cursor todavía no puede conectar Meister
El autor aún no ha puesto cómo instalarlo en el registro MCP
VS Code todavía no puede conectar Meister
El autor aún no ha puesto cómo instalarlo en el registro MCP
Otras apps que usan MCP, como Windsurf, Zed o Gemini CLI, añaden servidores de forma distinta. Míralo en la lista de apps
Ver todas las apps que usan MCP →
La configuración JSON está en “Para desarrolladores”, abajo
De un vistazo
- Descargas por semanai
- No está en npm/PyPI
- Dominio verificado
- ✓ qompass.ai
- Conexión
- –
- Última versióni
- 0.5.0
- Publicado en el registroi
- 18 nov 2026
- Último cambio de códigoi
- 19 nov 2026
- Creador
- qompassai
- Sitio web
- qompass.ai
- Estado en el registro
- Activo
Qué puede hacer
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisiones básicasi
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 20 nov 2026
- ✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con el dominio qompass.ai (el registro comprueba quién es dueño del dominio)
- ✓ Superada
Sigue en mantenimiento
Último cambio de código: ayer
- ✓ Superada
Tiene licencia
Usa Apache-2.0
- – No aplica
El endpoint responde
Este se ejecuta en tu computadora; no hay endpoint en internet
- – No aplica
Inicio de sesión con OAuth
Se ejecuta en tu computadora y usa ajustes locales en su lugar
- … Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Creadores: pedir otra revisión o avisar de un dato erróneo
Para autores: añade una insignia a tu README
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/servers/qompass-meister)Conversación
Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Reseñas de usuarios
Aún no hay reseñas
Comparado con otros en Juegos, deportes, comida y aprendizajei
- Más estrellas que el 0% de los otros 1623 servidores de esta categoría
- Publicado en el registro más recientemente que el 94% de los otros 1623 servidores de esta categoría
- Revisiones básicas iguales o mejores que el 99% de los otros 1623 servidores de esta categoría
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Preguntas frecuentes
¿Es seguro Meister?
Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
¿Qué claves o códigos necesita?
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
¿Se ejecuta en mi computadora o en la nube?
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
¿Sigue en mantenimiento?
El repo de GitHub cambió por última vez ayer, y la última versión (0.5.0) llegó al registro anteayer.
¿Qué apps pueden usarlo?
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code.
¿Qué puedo usar en su lugar?
En la misma categoría: Anime Garden, WilmAI, Lumify Sports Intelligence, Savecraft, GoodWatch
Alternativas parecidas
Misma categoría, otros creadores, comandos ya revisados. Primero los oficiales, luego por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
| Este Meister | Anime Garden | WilmAI | Lumify Sports Intelligence | Savecraft | GoodWatch | |
|---|---|---|---|---|---|---|
| Dónde se ejecuta | Se instala en tu equipo | Funciona en la nube, sin instalar nada | Se instala en tu equipo | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada |
| Necesita clave | No | No | No | Sí | No | No |
| Se añade con + en Claude | No | No | No | No | No | No |
| Revisiones básicas | 3/3 | 4/4 | 3/3 | 4/4 | 3/4 | 4/4 |
| Licencia | Apache-2.0 | AGPL-3.0 | MIT | MIT | Apache-2.0 | MIT |
| Precio | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro |
README del creador
Abrir el README
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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