原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Meister

✓ qompass.ai

注册名称ai.qompass/meister

安装方法

能做什么

Qompass SFW game maker MCP: authoring and project state for SFW games, with a live lane gate.

作者提供的原文

  • 连接方式 –
  • 账号或密钥 无需密钥
  • 分类 游戏、体育、美食与学习

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分12/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 Meister

开发者尚未在 MCP 注册表中填写安装方式

ChatGPT 暂时无法连接 Meister

开发者尚未在 MCP 注册表中填写安装方式

你可以改用这些方式

B · 游戏、体育、美食与学习 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Meister

开发者尚未在 MCP 注册表中填写安装方式

Cursor 暂时无法连接 Meister

开发者尚未在 MCP 注册表中填写安装方式

VS Code 暂时无法连接 Meister

开发者尚未在 MCP 注册表中填写安装方式

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Meister 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
已验证域名
✓ qompass.ai
许可证i
Apache-2.0
连接方式
–
最新版本i
0.5.0
发布到注册中心i
2026年11月18日
代码最后更新i
2026年11月19日
作者
qompassai
注册状态
活跃

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 qompass.ai 验证(注册中心会核实域名所有权)

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • ✓ 通过

    有许可证

    使用 Apache-2.0

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/qompass-meister.svg)](https://mcp.popnx.com/en/servers/qompass-meister)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“游戏、体育、美食与学习”中的其他服务器比较i

  • 星标数多于此分类中其他 1623 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1623 个服务器的 94% 更新
  • 基础检查结果等于或优于此分类中其他 1623 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Meister 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(0.5.0)于前天进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。

有什么可以替代它?

同一分类中有:Anime Garden, WilmAI, Lumify Sports Intelligence, Savecraft, GoodWatch

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

WilmAI

Finland's Wilma school system for parents and students: schedule, homework, exams and messages.

作者:aikarjal正在增长↓ 1399/周★ 89 整个仓库的星标11天前更新

在你的电脑上运行✓ 服务方 · wilm.ai

Savecraft

Savecraft serves real save game data and expert game knowledge to AI assistants.

作者:joshsymonds起步阶段★ 137个月前更新

在云端运行仓库已归档✓ 服务方 · savecraft.gg

GoodWatch

Find movies and TV shows, track watches, and get suggestions based on your taste.

作者:alp82起步阶段★ 50 整个仓库的星标31天前更新

在云端运行✓ 服务方 · goodwatch.app
与相似项目对比
本项
Meister
Anime GardenWilmAILumify Sports IntelligenceSavecraftGoodWatch
运行位置需要安装在电脑上在云端运行,无需安装需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否是否否
可在 Claude 中按 + 添加否否否否否否
基础检查3/34/43/34/43/44/4
许可证Apache-2.0AGPL-3.0MITMITApache-2.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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: qompass and content_label: sfw from 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 typed lane_mismatch; missing or other labels are refused as lane_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 candidate and 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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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 pass path 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 .aseprite sources, 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

只显示了开头部分;其余内容请在仓库中阅读